cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

Quartz
Adept II

codeXL sample projects using restrictive path, and some other installer issues and more

First, the installer should tell you, you need uninstall gdebugger & code analyst for it to work correctly.

While CodeAnalyst might be obvious, it still should check for them.

After installing to the default path, I try the sample programs to compile and I get:

1>------ Build started: Project: AMDTTeaPotLib, Configuration: Release Win32 ------

1>Error: Access to the path 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\CodeXL\Examples\Teapot\AMDTTeaPotLib\Release' is denied.

2>------ Build started: Project: AMDTTeaPot, Configuration: Release Win32 ------

2>Error: Access to the path 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\CodeXL\Examples\Teapot\AMDTTeaPot\Release' is denied.

========== Build: 0 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

It should *not* be installing things into a protected directory!

I also assume that is the reason I can't do openGL GPU performance counters, I get a popup error.

AMDCapture.PNG

This is on Vista 64bit.

CPU profiling seems to work fine.

Using version 1.1.2885.0

For the GPU, gdebugger did work fine before.

0 Likes
4 Replies
Quartz
Adept II

After uninstalling it, and reinstalling to D:\CodeXL, the sample *still* was installed to the wrong folder.

1>------ Build started: Project: AMDTTeaPotLib, Configuration: Release Win32 ------

1>Error: Access to the path 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\CodeXL\Examples\Teapot\AMDTTeaPotLib\Release' is denied.

2>------ Build started: Project: AMDTTeaPot, Configuration: Release Win32 ------

2>Error: Access to the path 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\CodeXL\Examples\Teapot\AMDTTeaPot\Release' is denied.

========== Build: 0 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

Can't do any GPU performance testing at all with this version using MSVC.

Next test will be running external version.

0 Likes

With external version, can't do anything with the GPU.

Both GPU performance counter and GPU application trace give this dialog, that is also shown when run within MSVC.

AMDCapture2.PNG

Setting logs to extensive show this:

////////////////////////////////////////////////////////////

// This File contains debug printouts

// Advanced Micro Devices, Inc.

// http://developer.amd.com/

////////////////////////////////////////////////////////////

### System information data:

### System DLL Versions:

##  - atioglxx.dll: 6.14.10.12002

##  - atio6axx.dll: 6.14.10.12002

##  - aticfx32.dll: 8.17.10.1172

##  - aticfx64.dll: 8.17.10.1172

##  - aticaldd.dll: 6.14.10.1741

##  - OpenCL.dll: 1.2.10.0

##

## OpenGL Renderer:

##  - Renderer Vendor: ATI Technologies Inc.

##  - Renderer Name: AMD Radeon HD 6800 Series

##  - Renderer Version: 4.2.12002 Compatibility Profile Context 9.12.0.0

##  - Renderer Type: Installable client

##

## Drivers versions:

##  - CAL version: 1.4.1741

##  - Catalyst version: 13.1

##

##   [18:14:30]   [130478188719]   [DEBUG]   [3776]   [apEventsHandler::handleDebugEvent]   [Events\src\apEventsHandler.cpp]   [468]   [Event handling ended]

(See attached file since it was too big for inline)

added dialog pic

0 Likes

Another issue, there is no way to turn off auto updates.

Even if you uncheck it, it still tries to check everytime VS is run.

Note, are these reports being read by the dev team ?

0 Likes

Hi Quartz,

Irrespective of the CodeXL install directory, the VS plug-in for CodeXL will be installed in the directory where VS is installed.

In your case, though you installed CodeXL in "D:\CodeXL", VS is still installed in "C:\Program Files (x86)" and hence the plug-in is installed in "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\CodeXL\".

By Default, automatic updater checks for the updates every day. You can change it to check every month by:

1. Launch VS.

2. Click on "CodeXL -> Help -> Check For Updates"

3. In "CodeXL - Check for Updates" dialog, change "Automatically check for updates every" drop-down list from "Day" to "Month".

4. Click "Close".

We do not officially supported Vista OS and we have not validated CodeXL functionality on Windows Vista.

Thanks,

Kalyan P

0 Likes