I agree that this is a Visual Studio issue; however, I am wondering if anyone
knows a workaround. I am not a Windows developer, but I figured that someone
on this list would have found a reasonable solution.
On Tuesday 28 August 2007 16:18:34 Andrew Maclean wrote:
> From memory, I am pretty sur
Hey Alexander,
>> Will this patch make it into CVS and eventually an upcoming CMake release?
>
> Done. It will be in cmake 2.6.0.
Excellent! Thanks again for the quick work on this.
>> I'm also curious, what would it take to get the D modules into the
>> default CMake install? Of course I wou
I do something like this (I think it was taken from the VTK CmakeLists.txtfile):
#-
# Let's use the highest warning level.
#-
IF(CMAKE_BUILD_TOOL
>From memory, I am pretty sure that this is a Visual Studio issue.
I agree that it is a pain but I think the solution outlined below is the
only one.
On 8/29/07, KSpam <[EMAIL PROTECTED]> wrote:
>
> One major annoyance that users have with CMake integration in VisualStudio
> is
> having to click
On Tuesday 28 August 2007 13:38, you wrote:
> Hi Alexander,
>
> Thanks very much for the patch! This does exactly what I needed! I
> just finished testing and the D module is now working great on all
> platforms and compilers finally.
>
> Will this patch make it into CVS and eventually an upcomin
One major annoyance that users have with CMake integration in VisualStudio is
having to click "Yes" to reload the project files after CMake regenerates
them. There is no "Yes to All" option. With hundreds of projects, it takes
a while to click all of the "Yes" buttons.
Does anyone know if the
> You can add the following to your toplevel CMakeLists.txt:
> SET(CMAKE_INCLUDE_CURRENT_DIR TRUE)
Yes, that's just what I want ! Thannks
> make.org/Wiki/CMake_Useful_Variables#Various_Options
That site's a bit scary, I'll stick with cmake.org for now!
;-/
___
On Tuesday 28 August 2007 14:33, Atwood, Robert C wrote:
> This seems to work (not quite as you suggest but similar)
>
> > 1.
> > INCLUDE_DIRECTORIES(${WIRS_BUILD_DIR}/path/to/.{cxx|h}) as
> > appropriate.
>
> You mean ${WIRS_SOURCE_DIR} ... and that seems to work but I am still
> puzzled why it is
This seems to work (not quite as you suggest but similar)
> 1.
> INCLUDE_DIRECTORIES(${WIRS_BUILD_DIR}/path/to/.{cxx|h}) as
> appropriate.
You mean ${WIRS_SOURCE_DIR} ... and that seems to work but I am still
puzzled why it is not included by default, it seems logical that your
own source dir
Atwood, Robert C wrote:
However, when I try to make the project with cmake, the tabinter.{cxx,h}
files are generated in the build directory, and the compiler cannot then
seem to locate the source directory where the 'eletable.h' file is
located.
Hi Robert,
Here's what I'd add to your CMakeLis
Hi Alexander,
Thanks very much for the patch! This does exactly what I needed! I
just finished testing and the D module is now working great on all
platforms and compilers finally.
Will this patch make it into CVS and eventually an upcoming CMake release?
I'm also curious, what would it take t
Hi,
I have a bit of a problem, which I can work around but would rather not
have to... I am using FLUID to make a FLTK interface, at this point just
to read some data into a customized structure. The structure definition
is in my header file 'eletable.h' in the source directory. The FLUID
file is
On Tuesday 28 August 2007 12:02, Tim Burrell wrote:
> Hi there,
>
> I'm currently working on a compiler module for CMake for the D
> programming language, and so far it's worked quite well, with one
> exception:
>
> The digital mars linker _requires_ that TARGET_LINK_LIBRARY paths have a
> trailing
Hi there,
I'm currently working on a compiler module for CMake for the D
programming language, and so far it's worked quite well, with one exception:
The digital mars linker _requires_ that TARGET_LINK_LIBRARY paths have a
trailing slash on them. To make matters worse it uses the same command
li
On Tuesday 28 Aug 2007 9:10:47 pm Matthew Woehlke wrote:
> The way I did this was to use the somewhat dubious solution:
>
> IF(PROJECT STREQUALS FOO)
> ADD_DIRECTORY(foo)
> ELSEIF(PROJECT STREQUAL BAR)
> ADD_DIRECTORY(bar)
> ELSE(PROJECT STREQUALS FOO)
> MESSAGE(FATAL_ERROR "You didn't tel
kitts wrote:
Anyway, I have a new set of projects and my current problem is that i have
some code that i share between projects. Once source can be shared not
binaries.
Code is organized as;
src/common
src/project1
src/project2
The CMakeLists.tst files are located inside for each project whic
Hendrik Sattler wrote:
But it's also a security nightmare: you cannot just update the lib, you also
have to relink the program.
Another reason: you can't statically link against GNU LGPL code without
getting into a huge mess of sending out half-linked binaries so that
users still have the fre
ADD_DEFINITIONS(-Wall)
should work for both the gnu c and c++ compiler and other compilers supporting
gnu option emulation.
You can also do:
make VERBOSE=1
on a unix system to see the commands being executed.
Regards,
Juan
-Original Message-
From: [EMAIL PROTECTED] on behalf of Mich
Am Dienstag 28 August 2007 14:54 schrieb Philip Lowman:
> Hendrik Sattler wrote:
> > Am Dienstag 28 August 2007 12:31 schrieb Convey Christian J NPRI:
> >> Thanks for the info. What a strange feature for CMake to lack! Does
> >> anyone know why this hasn't been implemented?
> >
> > OTOH, did you
Philip Lowman wrote:
I've never read that shared libraries are faster than static
executables. One would think that, if anything, all of the hoops the OS
has to run through to map all of the symbols would cause applications
that use shared libraries to be slower to startup then statically built
Dizzy wrote:
On Tuesday 28 August 2007 12:05:49 Martin Lütken wrote:
If not, then does anyone have an idea how hard it would be to add a
possiblity (command line option I guess) like that to the cmake source code
?
From a simple grep in the cmake CVS sources I think that to add such an
Michael Wagner wrote:
Hi,
Whenever I'm compiling, there are no warnings shown.
Is there a command or variable that can be used to turn on warnings?
I don't know of a specific CMake mechanism to turn on warnings. I
figure out which compiler I'm using and turn on flags manually by adding
the
Michael Wagner wrote:
Maybe somebody out there knows how to turn on warnings. (Hopefully you
are not all fearless coders that laugh in the face of warnings... ;-)
Real Programmers(tm) don't need warnings!
For mortals like myself, here's how I do it:
Go into the CMake cache via `make edit_cach
Hi,
Whenever I'm compiling, there are no warnings shown.
Is there a command or variable that can be used to turn on warnings?
When searching the wiki, the only information I found was this page:
http://www.cmake.org/Wiki/CMake_Platform_Dependent_Issues
which tells me the right flags for all the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hendrik Sattler wrote:
> Am Dienstag 28 August 2007 12:31 schrieb Convey Christian J NPRI:
>> Thanks for the info. What a strange feature for CMake to lack! Does
>> anyone know why this hasn't been implemented?
>
> OTOH, did you ask yourself why you
> > 1) We want to minimize the number of external dependencies
> required to
> > use the software, so that installing it requires a minimum of fuss.
>
> You could provide an additional binary package containing the
> needed libraries. Extremely easy ;)
I'd like to avoid packaging other project
Am Dienstag 28 August 2007 12:55 schrieb Convey Christian J NPRI:
> I'm creating installation packages for the software, and we have several
> goals:
>
> 1) We want to minimize the number of external dependencies required to use
> the software, so that installing it requires a minimum of fuss.
You
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Hendrik Sattler
> Sent: Tuesday, August 28, 2007 6:46 AM
> To: cmake@cmake.org
> Subject: Re: [CMake] Programs linked to .a or .so libraries?
>
> Am Dienstag 28 August 2007 12:31 schrieb Convey Chri
Am Dienstag 28 August 2007 12:31 schrieb Convey Christian J NPRI:
> Thanks for the info. What a strange feature for CMake to lack! Does
> anyone know why this hasn't been implemented?
OTOH, did you ask yourself why you actually want static linking? Sure, your
program will run that way but only
> -Original Message-
> From: Philip Lowman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 28, 2007 12:15 AM
> To: Convey Christian J NPRI
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Programs linked to .a or .so libraries?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Conve
> -Original Message-
> From: Philip Lowman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 28, 2007 12:15 AM
> To: Convey Christian J NPRI
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Programs linked to .a or .so libraries?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Convey
> -Original Message-
> From: Philip Lowman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 28, 2007 12:15 AM
> To: Convey Christian J NPRI
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Programs linked to .a or .so libraries?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Conve
On Tuesday 28 August 2007 12:05:49 Martin Lütken wrote:
> If not, then does anyone have an idea how hard it would be to add a
> possiblity (command line option I guess) like that to the cmake source code
> ?
From a simple grep in the cmake CVS sources I think that to add such an option
first woul
Martin Lütken a écrit :
Is it possible to change the default the default
filename "CMakeLists.txt" cmake looks for to something different ?
If not, then does anyone have an idea how hard it would be to add a
possiblity (command line option I guess) like that to the cmake source
code ?
No t
Is it possible to change the default the default filename "CMakeLists.txt"
cmake looks for to something different ?
If not, then does anyone have an idea how hard it would be to add a possiblity
(command line option I guess) like that to the cmake source code ?
Martin Lütken
Developer
Ne
Hello
I recently noticed that I am using add_definitions() for general compiler
flags (that have been checked previously with check_cxx_compiler_flag()) not
just "-D" flags. I also know this works not only when compiling with gcc
based compilers (including mingw on Windows) but also with cl.exe
36 matches
Mail list logo