Make mc.exe (Message Compiler) optional, for supporting MinGW cross-compiling #4642
Replies: 10 comments
-
Why don't you develop an portable Message Compiler compliant with the Windows Message Compiler? (With Poco of course!) |
Beta Was this translation helpful? Give feedback.
-
Seems overkill just for a header or two that need to be generated. Just including the header is a much simpler change. |
Beta Was this translation helpful? Give feedback.
-
In package mingw64-binutils-2.30-6.fc30.x86_64.rpm there is /usr/bin/x86_64-w64-mingw32-windmc, but to let it find by Poco cmake I had to create a symbolic link to mc.exe |
Beta Was this translation helpful? Give feedback.
-
MinGW has |
Beta Was this translation helpful? Give feedback.
-
In order to compile in ubuntu, I have to do:
|
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been open for 365 days with no activity. |
Beta Was this translation helpful? Give feedback.
-
Poco unable to find |
Beta Was this translation helpful? Give feedback.
-
It also works by simply specifying the full path to cmake via So I would not consider this as issue. |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been open for 365 days with no activity. |
Beta Was this translation helpful? Give feedback.
-
This issue was closed because it has been inactive for 60 days since being marked as stale. |
Beta Was this translation helpful? Give feedback.
-
Currently POCO will not build on systems without
mc.exe
. This is fine on Windows systems, where the Windows SDK can just be installed. However, this creates problems for cross-compiling Windows binaries on Linux. A pre-made header (see #2356 (comment) for one made for 1.9.0) should be included, and used whenevermc.exe
is not available.Beta Was this translation helpful? Give feedback.
All reactions