I'd like to set up a scheme in which I install a third-party SDK on
demand, before compiling the code that depends on it. In principle,
this is something that a pre_build target would help with, but that's
VS-specific.
Is there some other non-cumbersome approach I could use, short of
David Cole wrote:
When is on demand?
You could do this at CMake configure time if the on demand choice is
based on something known at CMake configure time.
That might do the trick.
Essentially, I'd like to be able to shove prebuilt object files and
headers for a third party library into a
Bill Hoffman wrote:
I will try to get this into 2.6.0 or 2.6.1.
Thanks, Bill. Hats off as usual for being accommodating and quick.
b
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I've spent about half the day thinking I was hallucinating because my
setting of CMAKE_OSX_SYSROOT was apparently not being picked up. The
reason, as it turns out, seems to be that CMake really does ignore this
variable unless you're doing a multi-architecture build.
It looks like I need one
On Windows and OS X, I notice that object files get put into a directory
prefixed with the current build type, e.g. Debug or Release. This
doesn't happen on Linux, so I can't have a single build tree with
multiple builds side by side in it. Is there some reason for this? The
variation in
I see info in the FAQ about adding a new build mode, but I don't know
how I might remove or rename one. For example, I'd like to get rid of
MinSizeRel. Does anyone have any suggestions?
Thanks,
b
___
CMake mailing list
CMake@cmake.org
Is there an appropriate way to cause an IDE like Visual Studio or Xcode
to present entries for source files such as .h files and .xml files,
which do not get compiled?
I'm currently listing those files as sources for library and executable
targets. This doesn't work very well: I have to make
I know that I can use set_source_files_properties to add to the
compilation flags used to build a single source file, but is there a way
to *remove* a compilation flag for one file?
My problem is that I build the source tree with -Wall -Werror, but one
source file contains a use of a bad
Jesper Eskilson wrote:
Those of you who haven't already read Version Control and 'the 80%'
should do so (http://blog.red-bean.com/sussman/?p=79) *before* forming
your opinion on centralized version control.
That article mixes some reasonable points with a good dose of nonsense,
so please
Mike Jackson wrote:
http://www.youtube.com/watch?v=4XpnKHJAok8
Git - straight from Linus.
I have this strange preference for my own voice and personality :-)
http://video.google.com/videoplay?docid=-7724296011317502612
b
___
CMake mailing
Alan W. Irwin wrote:
However, I admit to having no development experience with git or Mercurial.
Is there anything compelling (e.g., fewer bugs, better documentation, more
useful features aside from distributed?) about either over svn for
projects like CMake that use a centralized repo?
A
We have two sets of prebuilt libraries that we link against: debug and
release. These are organised in debug and release directories outside
of our source tree. Typically, the debug and release libraries have the
same names in each directory.
I can't find a good way to tell cmake that when
Alan W. Irwin wrote:
It was good to hear that make -j N normally works with CMake.
Yes indeed. I frequently run make -j70 across a 35-host dual-CPU
cluster using distcc, and every time I've updated CMake's files, it's
correctly rebuilt the makefiles before continuing.
b
I have two sibling directories. In one of them, a binary is built, and
in the other, that binary is packaged up using a custom command. Is
there a way in the DEPENDS clause to express this dependency?
b
___
CMake mailing list
CMake@cmake.org
14 matches
Mail list logo
