[cmake-developers] rc compiler on windows mingw
Pau Garcia i Quiles
pgquiles at elpauer.org
Thu Sep 22 10:55:36 EDT 2011
On Thu, Sep 22, 2011 at 4:42 PM, Bill Hoffman <bill.hoffman at kitware.com>wrote:
>
> This guy thinks he solved the issue by adding cl.exe to the path. If my
>> conjecture is correct, it was not cl.exe what was missing actually, but
>> rc.exe, which happens to live in the same directory as cl.exe. By
>> "adding cl.exe to the path" he actually added rc.exe to the path, which
>> is what CMake was looking for.
>>
>>
> Yes, that is exactly what happened in this case. However, the result was
> the same, he tried to build a project that most likely did not use
> resources, and it failed.
If you try the messed-up scenario I described, you will notice trying to
find the resource compiler actually clarifies the situation.
In the messed up scenario, you will end up having make, gcc, ld, etc, all
coming from different third-party components (msysgit, Strawberry Perl,
MinGW, Subversion, etc), but they will not be able to produce an executable,
or if they do, it will probably not run because it would have been linked to
a different version of some library. This happened to me when I had
Strawberry + msysgit + Qt Creator + WANDisco Subversion + OpenSSL-Win32:
CMake found all components, yet the executable ended up being linked to a
something that was not the first result in the path.
How does making the resource compiler mandatory help? Because third parties
that contains some elements from the GNU toolchain generally do not contain
windres, and if they do, somehow CMake ends up picking up an incompatible
combination of make, gcc, ld and windres.
> In this case, most likely we need to do a different association here...
>
> gcc -> windres
> cl -> rc.exe
>
> And not depend on the build tool.
>
>
I agree
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20110922/520780f5/attachment.html>
More information about the cmake-developers
mailing list