User forums > Help

[Resolved] VC Resource Compiler Issue

(1/3) > >>

Frank_CB:
Hello,

I'm using the most current release of CB 12.17, compiled from SVN source, on a desktop platform, using Windows 10 Home.

Using the newest release of Visual C++, from Microsoft, to provide the 64-bit compiler (cl.exe). resource compiler (rc.exe), linker (link.exe) and make (nmake.exe) executables, I can successfully generate Windows console-, gui-, mfc-, and wxWidgets-based applications outside of CB's IDE

However, only after copying rc.exe and rcdll.dll into an application's source folder, can I successfully generate the same applications within the IDE. CB's project files (.cbp) show a reference to 'windres', which is the resource compiler.from TDM-GCC-64's suite of executables. I found no referance to 'windres' in default.conf.

My work-around works, but it would be nice if I didn't have to resort to using it when I wanted to create a 64-bit application that includes resources.  Better yet, can someone explain why the work-around works?  It's almost like CB's looking for the resource compiler in the application's source folder and not where the toolchain says it's suppose to be.  Currently, rc.exe and rcdll.dll reside in a different folder than cl.exe, link.exe and nmake.exe.  That information is provided to the toolchain.

Regards,

Frank

P.S.  A .cbp file from a successfully built and executed wxWidgets sample is attached.

oBFusCATed:
What are you toolchain settings?
Can you post a log from a rebuild?

sodev:
Yes, rc.exe is part of the Windows SDK and the other files are part of the MSVC Toolchain, both reside in different locations. I add the other paths on the Additional Paths page of the Toolchain executables tab. Just for reference, with my MSVC 14 (Visual Studio 2015) Toolchain and the Windows XP Toolkit i use the following paths:

* Compiler's installation directory: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC
* Additional Paths:
* C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
* C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\bin
Your paths will be for sure different, escpecially if you use MSVC 14.1 (Visual Studio 2017) and the Non-Windows-XP-Toolkit in 64 Bit mode, but this should give you the idea.

A small addition after looking at your project file, i cannot recommend to put all this system specific paths of the compiler into the project file, it makes it too machine dependent, better put all these paths into the global compiler configuration. Take my old description as a reference http://forums.codeblocks.org/index.php/topic,22009.msg149847.html#msg149847.

BlueHazzard:
Can you open a ticket for this, so we can fix the msvc compiler search plugin?
Add the link to this forum post please

oBFusCATed:
Before a ticket, I think first we need to know if this is really a bug in the compiler.

Navigation

[0] Message Index

[#] Next page