On Mon 01 Jun 20:56 2009 Bill Hoffman wrote:
> e...@cs.bgu.ac.il wrote:
> > On Mon 01 Jun 15:28 2009 Bill Hoffman wrote:
> >> e...@cs.bgu.ac.il wrote:
> >>> On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
> >>> thanks for the tip, it solved the issue.
> >>>
> >>>
> >> I am glad that worked for you but
On Mon, Jun 1, 2009 at 10:36 PM, Philip Lowman wrote:
> On Mon, Jun 1, 2009 at 6:29 PM, Tyler Roscoe wrote:
>>
>> What are the pitfalls or difficulties in supporting this sort of
>> "cross-compiling" in Visual Studio?
>
> Two things come to mind:
>
> 1. find_library() (i.e. dependencies).. How wo
On Mon, Jun 1, 2009 at 2:12 PM, Sean Chittenden wrote:
> Ideally I'd like to see cmake(1) be able to issue the following commands:
>>>
>>> // Create foo_test
>>> gcc -o foo.o -c foo.c -DTESTING
>>> gcc -o foo_test foo.o
>>>
>>> // Create bar_test
>>> gcc -o foo.o -c foo.c
>>> gcc -o bar.o -c bar.
On Mon, Jun 1, 2009 at 6:29 PM, Tyler Roscoe wrote:
> What are the pitfalls or difficulties in supporting this sort of
> "cross-compiling" in Visual Studio?
Two things come to mind:
1. find_library() (i.e. dependencies).. How would you pick 64-bit vs.
32-bit?
2. When compile tests are run (e.g
Our developers are used to a single .vcproj that knows how to build both
32-bit and 64-bit versions of libraries. Under CMake, 32-bit and 64-bit
are considered separate platforms with separate generators and requiring
separate binary directories.
Conceptually and as a build engineer, this makes mo
Thanks. It works.
2009/6/1 Alexander Neundorf
> On Monday 01 June 2009, Dong Tiger wrote:
> > 2009/5/29 Alexander Neundorf
> >
> > > On Thursday 28 May 2009, idlecat...@gmail.com wrote:
> > > > Hi,
> > > >
> > > > This situation is:
> > > >
> > > > foo.h is generated from foo.x. And foo.h is in
>> I haven't tested this yet with a cmake build tree that has relative
>> entries in the CTestTest.cmake files so there may be issues but for
>> now this looks good enough to keep us going until a real solution is
>> in place.
>>
>
> Can you open a bug for this, and include a small complete example
On Mon, Jun 01, 2009 at 04:31:33PM -0400, Iman Brouwer wrote:
> #Add the source files
> FOREACH( cpp ${sources } )
> SET( arguments "${arguments} ${cpp}" )
> ENDFOREACH( cpp )
> add_custom_command( TARGET test COMMAND "script.py" "${arguments}" )
I think that will work if you get rid of the ""
Hello,
I'm trying to pass multiple arguments to a python script. The last arguments
are file names that are already in a cmake list (semicolon seperated
string).
Is it possible to pass the elements in this list to the python script as
separate arguments?
--
SET( sources s1.cpp s2.
On Monday 01 June 2009, Dong Tiger wrote:
> 2009/5/29 Alexander Neundorf
>
> > On Thursday 28 May 2009, idlecat...@gmail.com wrote:
> > > Hi,
> > >
> > > This situation is:
> > >
> > > foo.h is generated from foo.x. And foo.h is included by bar.h. And then
> > > bar.h is included by a lot of c fil
Ideally I'd like to see cmake(1) be able to issue the following
commands:
// Create foo_test
gcc -o foo.o -c foo.c -DTESTING
gcc -o foo_test foo.o
// Create bar_test
gcc -o foo.o -c foo.c
gcc -o bar.o -c bar.c -DTESTING
gcc -o bar_test foo.o bar.o
That help clarify? set_target_property() st
e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 15:28 2009 Bill Hoffman wrote:
e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
thanks for the tip, it solved the issue.
I am glad that worked for you but something else is wrong... How are
you linking bin/libs/libAgathaUtils.so' to
On Mon 01 Jun 15:28 2009 Bill Hoffman wrote:
> e...@cs.bgu.ac.il wrote:
> > On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
>
> >
> > thanks for the tip, it solved the issue.
> >
> >
>
> I am glad that worked for you but something else is wrong... How are
> you linking bin/libs/libAgathaUtils.s
2009/5/29 Alexander Neundorf
> On Thursday 28 May 2009, idlecat...@gmail.com wrote:
> > Hi,
> >
> > This situation is:
> >
> > foo.h is generated from foo.x. And foo.h is included by bar.h. And then
> > bar.h is included by a lot of c files. So actually every c files
> including
> > bar.h depends
Thanks for the tip! Searching the docs for the make_directory flag led me to
using:
FILE(MAKE_DIRECTORY directory1 directory2...)
Works perfectly!!!
Thanks again.
Gerrick
On 6/1/09 10:11 AM, "Tyler Roscoe" wrote:
> cmake -E make_directory
___
Powere
On Mon, Jun 01, 2009 at 09:02:31AM -0500, Gerrick Bivins wrote:
> I thought I could work around this by creating the directory during the
> build but I can't find any commands to do something similar to "mkdir".
Look at cmake -E make_directory.
You can run that as part of your build process with
Timothy M. Shead wrote:
Folks:
On a couple of occasions now I've recommended the use of relative paths
with the OSX bundle installer - this to install files within the bundle
in "nonstandard" locations. It would be good to hear from the CMake
gurus on whether relative paths are supported or
Hello,
I'm trying to use swig & cmake to generate java files for one of my
libraries. The problem I'm having is that I'd like to create a jar from
the output file but I don't know how to create a directory that swig can
write to from Cmake. I've specified:
SET(CMAKE_SWIG_OUTDIR
"${PROJECT_BIN
e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
thanks for the tip, it solved the issue.
I am glad that worked for you but something else is wrong... How are
you linking bin/libs/libAgathaUtils.so' to `bin/AgathaHud' ? You should
have something like:
target_link
On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
> > gmake[2]: *** No rule to make target in/libs/libAgathaUtils.so', needed
> > by in/AgathaHud'. Stop.
>
> Looks like your dependencies aren't set up correctly. You probably need
> something like:
>
> add_dependencies (AgathaHud AgathaUtils)
>
> The
20 matches
Mail list logo
