> > I have to revoke my last information. It does not work at least with a
> Visual Studio 2003 Project. Here, the system PATH is ignored.
> >
> > When I use an nmake makefile on the visual studio command line promt, it
> works fine - What is really kind of weird.
> >
> > Is there another way to te
Hey Philip,
thats good to know for most people using bison and flex!
In my special case, I have to add some stuff, as the old solaris version, I am
working with only supplies yacc instead of Gnu Bison and "lex" instread of
"flex".
Sadly these programs does not provide the same command line opt
On Tue, 2009-09-22 at 09:04 -0400, S Roderick wrote:
> On Sep 22, 2009, at 06:25 , Marcel Loose wrote:
>
> > On Mon, 2009-09-21 at 23:25 -0400, Philip Lowman wrote:
> >> On Mon, Sep 21, 2009 at 6:07 AM, Marcel Loose
> >> wrote:
> >>
> >>On Sun, 2009-09-20 at 19:32 -0400, Philip Lowman w
2009/9/22 Tyler Roscoe :
> On Tue, Sep 22, 2009 at 08:34:36PM +0200, Jeroen Dierckx wrote:
>> What we do in our build system is using file(GLOB to get all .cmake
>> files in a "targets" directory, and including those. That way, to add
>> additional targets, all the developers have to do is add a .c
Zitat von Philip Lowman :
FWIW, FindFLEX.cmake and FindBISON.cmake were both recently checked into
CMake CVS and might be worth a look.
http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindFLEX.cmake?root=CMake&view=log
http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindBISON.cmake?r
On Wed, Sep 23, 2009 at 5:52 AM, Hendrik Sattler wrote:
> Zitat von Philip Lowman :
>
>> FWIW, FindFLEX.cmake and FindBISON.cmake were both recently checked into
>> CMake CVS and might be worth a look.
>>
>>
>> http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindFLEX.cmake?root=CMake&view=lo
On Wed, Sep 23, 2009 at 3:36 AM, wrote:
> Hey Philip,
>
> thats good to know for most people using bison and flex!
>
> In my special case, I have to add some stuff, as the old solaris version, I
> am working with only supplies yacc instead of Gnu Bison and "lex" instread
> of "flex".
>
> Sadly th
Zitat von Philip Lowman :
AFAIK, this is possible with environment variables BISON_M4 or M4, see:
http://osdir.com/ml/parsers.bison.bugs/2007-05/msg00012.html
If that works, maybe the standard bison call should be replaced with a call
to a cmake script that sets this variable correctly.
Excel
Hi all,
I tried to figure this out by browsing the docs and the mailing lists,
but failed.
What changes to the cache file (CMakeCache.txt) will trigger a rerun of
CMake. AFAIK changes to CMAKE__COMPILER will do this, but are
there other situations?
My reason for asking this is that I was wonderi
Hi,
this thread got a bit off topic, so I try to focus that again, as I tried a lot
of things, but didn't get it to run:
In the end I would like to have some (lets say 10) packages (Installer bundles,
which I can create with cpack) with several executables and libraries. My
example over-simpli
On 09/23/2009 09:05 AM, th@gmx.de wrote:
Hi,
this thread got a bit off topic, so I try to focus that again, as I tried a lot
of things, but didn't get it to run:
In the end I would like to have some (lets say 10) packages (Installer bundles, which I
can create with cpack) with several exe
On Wed, Sep 23, 2009 at 03:02:31PM +0200, Marcel Loose wrote:
> What changes to the cache file (CMakeCache.txt) will trigger a rerun of
> CMake. AFAIK changes to CMAKE__COMPILER will do this, but are
> there other situations?
Don't all changes to the cache trigger a CMake rebuild?
> My reason for
On Wed, Sep 23, 2009 at 11:08:38AM +0200, Jeroen Dierckx wrote:
> 2009/9/22 Tyler Roscoe :
> > On Tue, Sep 22, 2009 at 08:34:36PM +0200, Jeroen Dierckx wrote:
> >> What we do in our build system is using file(GLOB to get all .cmake
> >> files in a "targets" directory, and including those. That way,
Sending this back to the list for completeness.
On Wed, Sep 23, 2009 at 08:31:33AM -0600, Dixon, Shane wrote:
> You were right, it did end up being recursive. Each time I configured, it
> would keep appending MyProg-${VERSION} to the already existing path. I got
> around it by doing this:
>
>
hm, right - this would solve my problem, but sadly writing everything in one
CMakeLists.txt file was not a clever idea, as the projects should be build
independently.
Another solution I had (someone posted that) is creating a subdirectory for
every project and place the specific CMakeLists.txt
On Wednesday 23 September 2009 10:25:37 am th@gmx.de wrote:
> hm, right - this would solve my problem, but sadly writing everything in
> one CMakeLists.txt file was not a clever idea, as the projects should be
> build independently.
>
> Another solution I had (someone posted that) is creating a
th@gmx.de wrote:
hm, right - this would solve my problem, but sadly writing everything in one
CMakeLists.txt file was not a clever idea, as the projects should be build
independently.
Another solution I had (someone posted that) is creating a subdirectory for
every project and place the s
We use the RUNTIME_OUTPUT_DIRECTORY property to specify runtime
location for each target:
set_target_properties(bla-bla-bla
PROPERTIES
RUNTIME_OUTPUT_DIRECTORY
${CMAKE_BINARY_DIR}/Execute/${CMAKE_BUILD_TYPE})
)
I hope it helps.
Jeroen Dierckx:
Hi,
In Windows, we need to copy a bunch of
On Wed, Sep 23, 2009 at 9:06 PM, Anatoly Shirokov wrote:
> We use the RUNTIME_OUTPUT_DIRECTORY property to specify runtime location
> for each target:
>
> set_target_properties(bla-bla-bla
>PROPERTIES
>RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}*/Execute/*${CMAKE_BUILD_TYPE})
>
> )
> I h
Visual Studio supports having solution files where the solution can set the
supported platform to x64 and yet have individual projects in the solution
build for the Win32 platform despite having the solution set to x64. Can I
configure CMake to set up projects/solutions in this fashion?
Thanks,
2009/9/20 Philip Lowman :
> On Sun, Sep 20, 2009 at 9:33 PM, Alain Leblanc wrote:
>>
>> Thanks for the reply. I'm experienced with GCC, but just really
>> starting with VC++, and I should probably spend more time learning it.
>>
>> I am using FindBoost and I know it finds my boost installation ok
On Wed, Sep 23, 2009 at 01:36:51PM -0600, Steven Wilson wrote:
> Visual Studio supports having solution files where the solution can set the
> supported platform to x64 and yet have individual projects in the solution
> build for the Win32 platform despite having the solution set to x64. Can I
>
Steven Wilson wrote:
Visual Studio supports having solution files where the solution can set
the supported platform to x64 and yet have individual projects in the
solution build for the Win32 platform despite having the solution set to
x64. Can I configure CMake to set up projects/solutions i
On Wed, Sep 23, 2009 at 3:36 PM, Steven Wilson
wrote:
> Visual Studio supports having solution files where the solution can set the
> supported platform to x64 and yet have individual projects in the solution
> build for the Win32 platform despite having the solution set to x64. Can I
> configur
I just include some CMake code to copy the Qt Dlls from the Qt
installation directory into the local Debug or Release directories.
Kinda clunky but gets the job done.
--
Mike Jackson
On Sep 23, 2009, at 3:09 PM, Jeroen Dierckx wrote:
On Wed, Sep 23, 2009 at 9:06 PM, Anatoly Shirokov
wr
On Wednesday 23 September 2009 17:45:39 Tyler Roscoe wrote:
> On Wed, Sep 23, 2009 at 03:02:31PM +0200, Marcel Loose wrote:
> > What changes to the cache file (CMakeCache.txt) will trigger a rerun of
> > CMake. AFAIK changes to CMAKE__COMPILER will do this, but are
> > there other situations?
>
> D
Hello Everyone,
I am attempting to make a package for OS X using CPack. One of the items I am
installing is a .app bundle that is generated in an external project (not
CMake).
I am trying to install the .app with an INSTALL(DIRECTORY ) command and
adjusting the permissions as required.
On Wed, Sep 23, 2009 at 10:29 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> I just include some CMake code to copy the Qt Dlls from the Qt installation
> directory into the local Debug or Release directories. Kinda clunky but gets
> the job done.
>
We do it in the same way actually,
On Wed, Sep 23, 2009 at 10:28:04PM +0200, Marcel Loose wrote:
> Well, I created a macro (inspired by the KDE macro in kdelibs,
> "macro_optional_add_subdirectory") that will only do add_subdirectory() if
> the
> directory actually exists (useful to do partial builds of large projects).
> Inside
29 matches
Mail list logo
