Good day!
You can try the experimental installer (based on IFW generator) from my website:
http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-rc3-win64-x64.exe
You can also try the online version, which is based on code from branch
"master":
Dear Sirs,
There are only 32Win version of CMake( cmake-3.5.0-rc3-win32-x86.msi or
cmake-3.5.0-rc3-win32-x86.zip ) on your web page( https://cmake.org/download/
). When will the version for 64Win available?
Thank you for the help!
Ning.
==
LI, Ning. Ph.D.
Seems to me like C# support should work just fine with other generators: ninja,
nmake, and UNIX Makefiles included. Especially with mono on Linux/Mac.
David
> On Mar 7, 2016, at 2:12 PM, Brad King wrote:
>
>> On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP
We have to call :
fixup_bundle("${CMAKE_INSTALL_PREFIX}/../test"...
to fix an optional test folder installed near the app.
verify_app will later compare a path like C:/program/app/../test to
C:/program/test and state they are inequal while they point to the same
file.
That's why I have to call
On Mon, Mar 7, 2016 at 8:06 PM, Brad King wrote:
> On 03/07/2016 02:49 PM, Bruce Stephens wrote:
>> Moving the method into there worked cleanly.
>
> Thanks. I split that into a separate commit:
Thanks. I wondered whether or not to do that separately.
--
Powered by
On 03/07/2016 02:49 PM, Bruce Stephens wrote:
> Moving the method into there worked cleanly.
Thanks. I split that into a separate commit:
cmCommonTargetGenerator: Adopt AppendOSXVerFlag method
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1f2b39c6
Then I applied the main change:
On Mon, Mar 7, 2016 at 6:06 PM, Brad King wrote:
> On 03/01/2016 04:58 PM, Bruce Stephens wrote:
>> I just copied the relevant code from the Makefiles generator.
>
> Thanks. Instead of copying, please look at moving the relevant
> methods up to cmCommonTargetGenerator so
On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote:
> The part that probably needs most additional work is all the
> C# detection and configuration part in the module scripts.
In your branch Modules/CMakeDetermineCSharpCompiler.cmake currently
has a lot of logic and environment checks
On 03/01/2016 04:58 PM, Bruce Stephens wrote:
> I just copied the relevant code from the Makefiles generator.
Thanks. Instead of copying, please look at moving the relevant
methods up to cmCommonTargetGenerator so it can be shared between
the two generators instead.
Thanks,
-Brad
--
Powered
On 03/02/2016 04:36 AM, Richard Wiedenhöft wrote:
> The way I see it there is no downside to this and it spares me (and
> hopefully others) from polluting my CMakeLists.txt with
> "set(CMAKE_EXPORT_COMPILE_COMMANDS ON)" making them more readable.
The down side is it takes longer to generate and
On 03/01/2016 03:15 AM, Antonio Perez Barrero wrote:
> Use recommended case for variable names. i.e. matching name of the
> module as passed to `find_package`.
>
> For backwards compatibility, the upper case versions of both input and
> output variables are used and defined when appropriate.
On 03/04/2016 12:17 PM, Benjamin Ballet wrote:
> The fail occurs during verify_app in the function gp_resolved_file_type
> from module GetPrerequisites. This function test if two paths are equal
> without translating them to there canonical form before.
[snip]
>
On 02/29/2016 12:35 PM, Philippe Proulx wrote:
> This patch adds the FindLTTngUST module which can be used to find
> the LTTng-UST library. It sets result variables and creates an
> imported target, LTTng::UST.
Thanks, applied:
Add FindLTTngUST module to find LTTng-UST library
13 matches
Mail list logo