You probably want to use the execute_process() on "llvm-config --cppflags",
then "llvm-config --ldflags", etc. and store each into a variable using a
regular expression if necessary to parse the output. From there you can
call include_directories(), add_definitions(), and target_link_libraries()
a
Hi,
I am having some difficulties determining how to work with a back quoted
arguments generator using CMake. I.e. something like this-
g++ -g -c Exp.cpp `llvm-config --cppflags --ldflags --libs core jit native`
Any advice/tips would be appreciated.
Thanks in advance,
Carter.
___
No. It's supposed to return the actual string that is referenced by the
thing being analyzed. But you can call gp_resolve_item to get the full
path... (There is a reason for this, although I can't remember what it is at
the moment... If I think of it, I'll reply again.)
>From commentary in the midd
Is get_prerequisites() supposed to return absolute paths all the time?
For example, on the Mac, I've got some frameworks in /Library/Frameworks
that I may want to copy if they might not exist on other Macs. When I
call get_prerequisites(), getting "foo.framwork/" instead of
"/Library/Framewor
On Fri, Jul 17, 2009 at 08:32:38PM +0200, Jörg Förstner wrote:
> We use gcc's option "-frandom-seed=", which uses a given value as a
> starting point for it's random number generator.
> As every file shall have a unique random seed, we calculate the MD5 checksum
> of each source file "on the fly"
So I would love to see a corollary to BundleUtilities.cmake for Mac on
Windows and Linux, too.
Using GetPrerequisites to gather the set of dependent files is obviously the
first step.
Then, on Windows, a function that installs all the dependent dlls to the
same location as the executable would be
So I'm using GetPrequisites.cmake to gather dependencies.
Are there any examples, tips, etc.. for using this?
With the results I'm getting back, I do a
file(INSTALL ... ) because that's what I see in the cmake_installcmake
file. Should it be documented?
But these files I'm getting back are soft
Hi,
I've a problem converting one important feature of our old make-build-process
to the new cmake-build-process.
The problem:
In our old build process, each object file was binary different from one build
run to another.
This problem was caused by gcc using randomly generated symbol names.
Th
I have this snipped in my cmakelists:
IF( EXISTS "/someabsolutedirectory/unixem-1.8.2/include/glob2.h" )
message( "/someabsolutedirectory/unixem-1.8.2/include/glob2.h exists" )
ENDIF( EXISTS "/someabsolutedirectory/unixem-1.8.2/include/glob2.h" )
INCLUDE_DIRECTORIES( "/someabsolutedirectory/u
This is similar to a thread a while back:
http://www.cmake.org/pipermail/cmake/2009-April/028419.html
I suggested comparing the CMakeCache.txt files before and after a configure
to get a list of relevant configuration changes and adding them to the
command line.
James
On Fri, Jul 17, 2009 at 7:
I think you can write a starter cmakecache in an empty build directory
consisting of just the non-default options you want and and then run
cmake on that. It will fill in the rest of what it needs if you've
provided a consistent set that doesn't need to ask you anything.
That is what dashboards do
Hi,
I did a quick search on google, and found nothing. But in case I
missed something, is anyone using netbeans with cmake ? Has anyone
worked on nbproject generator ?
Thanks,
--
Mathieu
___
Powered by www.kitware.com
Visit other Kitware open-sourc
Hi Bill and Eric,
I see your points about the implementation but I think you are thinking to
something different that I have in my mind.
I am not interested in portability. When I try to compile a big project (eg
paraview) the -gui is a very good tool, due to its incremental support. Then I
g
On Thursday 16 July 2009, Mathieu Malaterre wrote:
> On Thu, Jul 16, 2009 at 5:01 PM, Mathieu
>
> Malaterre wrote:
> > On Thu, Jul 16, 2009 at 4:58 PM, Michael
> >
> > Jackson wrote:
> >> On Jul 16, 2009, at 10:41 AM, Mathieu Malaterre wrote:
> >>> On Thu, Jul 16, 2009 at 4:32 PM, David Cole
wrote
14 matches
Mail list logo