- Original Message -
From: Olivier Tournaire
Date: 2/21/2008 3:54 AM
I am also very intersted in this change. I usually put all my *.exe in
one folder, say "bin". For release version, with the name
$(ProjectName).exe, and Debug version $(ProjectName)-D.exe.
As far as I understand, this
- Original Message -
From: Brandon Van Every
Date: 2/5/2008 7:23 AM
On Feb 5, 2008 6:50 AM, John Spray <[EMAIL PROTECTED]> wrote:
Is it possible to build certain objects for one architecture and
certain objects for another?
Not in the same build. You'd need 2 different invocati
*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of
*Malhotra, Anupam
*Sent:* 15 January 2008 06:37
*To:* cmake@cmake.org
*Subject:* [CMake] Adding Custom Build Types
Now In my project I don’t want these build types. I want custom build
types like MD, MT, MDd, MTd, ML etc (for
- Original Message -
From: James Mansion
Date: 1/4/2008 3:38 PM
> Gonzalo Garramuño wrote:
>> In summary, once you use git, if you are like me, you'll realize
that you've been doing source version control wrong all these years *sigh*.
>>
> Does git work on Win32?
Pretty well, I've found
- Original Message -
From: Brandon Van Every
Date: 12/14/2007 12:04 PM
Certain CMake people want to *say* it was conclusive, so that the
issue will go away, but it wasn't conclusive. In particular, I have
to note the self-selecting nature of the CMake community. If you
stick around and
Philip Lowman wrote:
Josef Karthauser wrote:
Hi there again,
I’m using cmake to create some visual studio projects, and want to
include some non-C files (config.txt for instance) into the vcproj file
so that my Visual Studio users can edit the file from within the IDE.
I can’t add them usi
Sylvain Benner wrote:
What's the canonical way of marking a file as being excluded from a
given Visual Studio configuration?
No this is not supported.
I think it's better to use preprocessor to do this kind of stuff.
In my patched version at:
svn co svn://svn.luaplus.org/CMake/patches/All CMa
KSpam wrote:
This was an annoyance I had with Visual Studio as well, and I was able to work
around it fairly easily. I have CMAKE_CONFIGURATION_TYPES set when I am
building in Visual Studio. I expect that this would be similar for Xcode.
All I do is prepend "../" to the output name, and I se
Sylvain Benner wrote:
What about the debug/optimized flags for TARGET_LINK_LIBARIES()? Do
these work right now by taking advantage of the fact that Debug,
Release, MinSizeRel, and RelWithDebInfo are hardcoded?
We had to "upgrade" the cmTarget sources to add the new configuration
type and then
I was wondering if there is a Jamfile generator for CMake for either
Perforce Jam or Boost Jam? I'm doing build system experiments, and I'd
like to export the CMakeLists.txt contents to alternative build systems.
Thanks.
Josh
___
CMake mailing list
Luigi Calori wrote:
Probably dumb question, but was not able to found hints on docs:
Visual Studio projects generated do append Debug / Release to the
EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH paths.
Is there a way to avoid this and force them to generate straight
inside EXECUTABLE_OUTPUT_
Bill Hoffman wrote:
Kovarththanan Rajaratnam wrote:
To compare things, I've downloaded the Windows version and it seems
to list all the Visual Studio generators. Would I have to compile my
own version of CMake under Cygwin? If so, do I need to pass special
parameters to ensure that the Visual
Brandon Van Every wrote:
On 6/9/07, Joshua Jensen <[EMAIL PROTECTED]> wrote:
What is Kitware's interest in full Visual Studio C# support in CMake?
10 months ago, Brad King wrote in
http://public.kitware.com/pipermail/cmake/2006-August/010528.html
is there any development (pl
Brandon Van Every wrote:
On 6/9/07, Joshua Jensen <[EMAIL PROTECTED]> wrote:
My only concern is maintaining a fork to do this. I already have a
forked CMake with various fixes to the Visual Studio and Xcode support.
Despite increasing usability in these environments, the interest level
Brandon Van Every wrote:
On 6/6/07, Joshua Jensen <[EMAIL PROTECTED]> wrote:
So, for fun, I was trying to implement C# support through some extra
.cmake files.
It would be good to get a wiki page up about C# issues, so there's
some stickiness to various people's efforts. When
Pau Garcia i Quiles wrote:
The developers of Qyoto (the C# binding to Qt) have written a
FindMono.cmake which might be useful:
http://websvn.kde.org/trunk/KDE/kdebindings/cmake/modules/FindMono.cmake
This was useful, but I never really made it work well.
* ${CMAKE_CURRENT_SOURCE_DIR}/ must be
Brandon Van Every wrote:
CMake users: what source control systems are you using?
We were using Subversion, but we've migrated to Perforce.
Josh
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
So, for fun, I was trying to implement C# support through some extra
.cmake files. This won't be good enough to work with Visual Studio's
MSBuild, but I wanted to give it a start.
I ran into an interesting issue.
A simple C# command line appears as follows:
csc /out:MyApp.exe /target:exe
Christoph John wrote:
I am using cmake to generate visual studio 8.0 makefiles. Currently the sources
per project are displayed in two sections in VS in a Header and Source section.
Now my question: Can I define a own section structure where the sources should
be displayed in and how can I do
So, I have an interesting problem when using CMake (latest CVS).
I set the EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH to be the
following:
SET (LIBRARY_OUTPUT_PATH ${PROJECT_BINARY_DIR}/image CACHE PATH
"Output location for LuaPlus libraries")
SET (EXECUTABLE_OUTPUT_PATH ${PROJECT_B
Bill Hoffman wrote:
Joshua Jensen wrote:
The following patch fixes the issue.
Thanks!
$ cvs commit -m "ENH: @ must be escaped in xcode projects"
cmXCodeObject.cxx
Checking for path: /cvsroot/CMake/CMake/Source
Unrestricted user: hoffman
/cvsroot/CMake/CMake/Source/cmXCodeOb
After inserting the following into my CMakeLists.txt:
SET_TARGET_PROPERTIES(MyLibrary PROPERTIES BUILD_WITH_INSTALL_RPATH 1
INSTALL_NAME_DIR @executable_path)
XCode stopped opening the .xcodeproj. This was due to an unquoted line
in project.pbxproj:
INSTALL_NAME = @executable_path
It shou
Bill Hoffman wrote:
Rob Mathews wrote:
To reproduce, take CMake 2.4.1 from CVS and build it.
Open the CMake.sln file, right click on CMake project, choose
properties.
Look Properties->C/C++->General tag, the "Debug Information Format"
field. It says "Disabled".
Does it work in CMake 2.4.6?
Stra
There is a provided simple patch for this attached to the bug at
http://www.cmake.org/Bug/bug.php?op=show&bugid=4338&pos=5. Is there any
chance this can find it into the CVS build of CMake?
Thanks.
Josh
___
CMake mailing list
CMake@cmake.org
http://
With latest CVS (in an attempt to see if the problem was fixed), I was
attempting the following:
SET_SOURCE_FILES_PROPERTIES(Somefile.dat PROPERTIES
MACOSX_PACKAGE_LOCATION Resources)
This works great and does exactly what I expected it would do (assuming
it doesn't copy each and ever
Rob Mathews wrote:
Anybody out there used CMake to generate C# .vcproj files?
That is, I've got a large C++ code base, and a few C# projects on the
side, and I want to use CMake for the C# projects as well.
I'd like to know what ideas people have on this, too. There are no
references to .
Jesper Eskilson wrote:
2007/5/18, Joshua Jensen <[EMAIL PROTECTED]>:
Custom build types don't work under Visual Studio. The following
"patches" (not really a patch but the best I could do at the moment)
gives you custom build types under Visual Studio. These are agai
Jesper Eskilson wrote:
Hi all,
I tried following the instructions on the wiki on how to define my own
build type (configuration), however the new build type ("Develop")
does not show up as a valid solution configuration in Visual Studio.
Why is that?
Custom build types don't work under Visual S
I have some questions about the process by which the INSTALL() command
works:
---
Despite CMAKE_BUILD_TYPE being set to Debug in CMakeSetup for my NMake
project, cmLocalGenerator::GenerateInstallRules() creates
cmake_install.cmake files with a default line of
SET(CMAKE_INSTALL_CONFIG_NAM
Mike Jackson wrote:
On May 11, 2007, at 7:55 AM, Angel Riesgo wrote:
My second question is how I can prevent CMake from adding "debug" and
"release" intermediate directories to the output path. In the
CMakeLists.txt file, I am setting LIBRARY_OUTPUT_PATH to a path
ending in lib/win/, but the V
Bill Hoffman wrote:
Joshua Jensen wrote:
Well, now that I know what it is, I'll just turn off the
MACOSX_BUNDLE flag for the time being. I'll watch CVS for a fix.
It is broken for all targets in CVS at the moment for some reason
I would recommend not using cvs...
Unfortunately,
Bill Hoffman wrote:
Joshua Jensen wrote:
ersion of CMake are you using? Also, I don't think CMake has
anything to do with the clean target, it is managed by Xcode itself.
It does seems that this is currently broken in CVS, I am looking into
the issue. I have to figure out some w
Bill Hoffman wrote:
Joshua Jensen wrote:
Upon using CMake with Xcode and instructing CMake to generate
application bundles, I've run into the following issues:
* When I make a change to a static library, the executable doesn't
relink. I have to rm it from the application bun
me.
If anyone knows how to fix this, please let me know.
Thanks.
Joshua Jensen
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Bill Hoffman wrote:
Joshua Jensen wrote:
* Reservation of a 10 megabyte stack in Windows-cl.cmake is
overkill. The default is 1 megabyte. Why is this here? I removed it.
I guess this goes back to the projects that CMake was originally
developed for. But now due to backward compatibility I
ed over CMake in the past, and I'm glad it caught my eye this
time around. It is a most excellent product, and I look forward to
working with it more.
Thanks.
Joshua Jensen
---
Windows-cl.cmake:
* Reservation of a 10 megabyte stack in Windows-cl.cmake is overkill.
The default i
36 matches
Mail list logo
