Hi Brad,
I am glad it was something this simple (even though with far-reaching
consequences)! It is not something I could have found out myself.
Regards,
Arjen
On 2010-09-28 16:18, Brad King wrote:
On 9/28/2010 6:35 AM, Arjen Markus wrote:
for the PLplot project (http://plplot.sf.net) I have
On Tue, Sep 28, 2010 at 6:23 PM, Ryan Pavlik wrote:
> In most cases, you won't need more than one project call - each target
> (add_executable, etc) creates a visual studio project, so the only
> reason I can think of that you'd necessarily have multiple project
> calls is if you have a subdirecto
In most cases, you won't need more than one project call - each target
(add_executable, etc) creates a visual studio project, so the only
reason I can think of that you'd necessarily have multiple project
calls is if you have a subdirectory that can also stand alone as a
separate build.
You might
On 09/28/2010 05:35 PM, David Aldrich wrote:
> Hi
>
> I am writing CMakeLists.txt files for my C++ application. Initially I set the
> C++ compiler flags by setting CMAKE_CXX_FLAGS:
>
> set( CMAKE_CXX_FLAGS "-Wall -m64 -O3 " )
>
> Then I realised that those flags get passed to the linker as well
Is there a reason that incremental linking is enabled by default with
generated output from cmake? Hmm and it's not disabled in release
mode... I went to check to see what the option actually does for (or
to) me..
-- from http://msdn.microsoft.com/en-us/library/4khtbfyf(v=vs.80).aspx --
An incre
Is there a way to specify what the name of the solution file should
be? Currently it's named from the last PROJECT in a CMakeLists.txt.
I would prefer that it be the first name... I see methods of setting
output files for particular projects, but not the solution
__
The short answer is then: there is no such an option.
Oki doki, thank you.
Best Regards,
Laszlo Papp
On Tue, Sep 28, 2010 at 12:25 PM, Alexander Neundorf
wrote:
> On Tuesday 28 September 2010, Laszlo Papp wrote:
>> It is not a KDE project ...
>
> It was just meant as inspiration.
> And if you wa
On Tuesday 28 September 2010, Laszlo Papp wrote:
> It is not a KDE project ...
It was just meant as inspiration.
And if you want you can of course use the code for the install dirs from
FindKDE4Internal.cmake, it's BSD licensed.
Alex
___
Powered by www
It is not a KDE project ...
Best Regards,
Laszlo Papp
On Tue, Sep 28, 2010 at 11:29 AM, Alexander Neundorf
wrote:
> On Tuesday 28 September 2010, Laszlo Papp wrote:
>> Hi,
>>
>> Is there such an environment variable, like in case autoconf:
>> --localstatedir=DIR modifiable single-machine d
On Tuesday 28 September 2010, Laszlo Papp wrote:
> Hi,
>
> Is there such an environment variable, like in case autoconf:
> --localstatedir=DIR modifiable single-machine data [PREFIX/var]
>
> There are options like CMAKE_INSTALL_PREFIX, SYSCONF_INSTALL_DIR, but
> not this one. I can make an ow
On Tuesday 28 September 2010, Marcel Loose wrote:
> Hi all,
>
> I was wondering how I could generate a list of user-definable CMake
> variables. This list, with a brief help per variable, would be *very*
> useful for the end-user. It's a bit like the well-known "configure
> --help" which gives you
Hi Michael,
so if I get you right I should organize my library as follow:
src/
Compiler/G95_Fortran.cmake
CMakeLists.txt
my_general_f90_src_files
special_flag_src/
Compiler/G95_Fortran.cmake
CMakeLists.txt
my_special_f90_src_files
where the nested CMake
Hi All,
I have project which (cross-)compile some simple C applications
with some bare CMake statement like this:
add_executable(myapp myapp.c)
no target_link_libraries, no dep, etc...
I want to build fully static executable (even for libc etc...)
Currently I do:
set_target_properties(myapp P
Hi,
I am seeking for advise. I would like to run some CTest tests from the build
tree, which require C++ or Python modules created in other project directories
(packages). For this I need to build correctly the LD_LIBRARY_PATH and
PYTHONPATH and use the command set_property(TEST xxx PROPERTY
Hi
I am writing CMakeLists.txt files for my C++ application. Initially I set the
C++ compiler flags by setting CMAKE_CXX_FLAGS:
set( CMAKE_CXX_FLAGS "-Wall -m64 -O3 " )
Then I realised that those flags get passed to the linker as well, which seemed
a bit untidy. So I now use add_definitions in
Marcel,
We use a 'bootstrap' CMakeCache.txt file that has README-like full
documentation for each user settable variable. This way a new developer can
copy the bootstrap CMakeCache.txt file to his/her build directory and edit
the file variable-by-variable before running cmake.
Something like:
#
On 28. Sep, 2010, at 16:08 , pellegrini wrote:
> Hello everybody,
>
> I have a library for which almost all the files should be compiled (e.g. g95)
> with the same compilation flags (that I will call later flag_debug,
> flag_release ...) excepted a few ones for which I have to use slightly
>
On 9/28/2010 6:35 AM, Arjen Markus wrote:
> for the PLplot project (http://plplot.sf.net) I have tried to use
> the Visual Studio 2008 generator in combination with Intel Fortran
> (version 11.1). Generating the solution and the project files
> works fine, but when I try to build it all, I get erro
Hello everybody,
I have a library for which almost all the files should be compiled (e.g.
g95) with the same compilation flags (that I will call later
flag_debug, flag_release ...) excepted a few ones for which I have to
use slightly different compilation flags (called later flag1_debug,
fla
On 9/28/2010 5:43 AM, David Cole wrote:
Why do you think this is incorrect?
Either $(Configuration) or $(IntDir) should be acceptable locations for
obj files...
This was a bug, Brad checked in the fix into next.
-Bill
___
Powered by www.kitware.com
Hello,
for the PLplot project (http://plplot.sf.net) I have tried to use
the Visual Studio 2008 generator in combination with Intel Fortran
(version 11.1). Generating the solution and the project files
works fine, but when I try to build it all, I get error messages
about various symbols being
Hi,
Is there such an environment variable, like in case autoconf:
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
There are options like CMAKE_INSTALL_PREFIX, SYSCONF_INSTALL_DIR, but
not this one. I can make an own one, I am just out of the curiosity
whether there is an int
Why do you think this is incorrect?
Either $(Configuration) or $(IntDir) should be acceptable locations for obj
files...
On Sun, Sep 26, 2010 at 11:40 AM, J Decker wrote:
> this is the sample cmakelists that causes bad output...
>
> --
>
> cmake_minimum_required(VERSION 2.8)
>
> pr
2010/9/28 Marcel Loose :
>>
>> You may want to call your target "help" but it would conflict/override
>> the cmake builtin "help" target
>> (at least for makefile generator) which display the list of available
> target.
>>
>> This work AFTER cmake has been run. It could be run before as well
> usin
On 28. Sep, 2010, at 11:03 , Marcel Loose wrote:
> On Tue, 2010-09-28 at 10:43 +0200, Michael Wild wrote:
>> On 28. Sep, 2010, at 10:12 , Marcel Loose wrote:
>>
>>>
>>> On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
>>>
> Hi all,
>
> I was wondering how I could generate a list of
On Tue, 2010-09-28 at 10:42 +0200, Eric Noulard wrote:
> 2010/9/28 Marcel Loose :
> >
> > On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
> >
> >> > Hi all,
> >> >
> >> > I was wondering how I could generate a list of user-definable
CMake
> >> > variables. This list, with a brief help per variable,
On Tue, 2010-09-28 at 10:43 +0200, Michael Wild wrote:
> On 28. Sep, 2010, at 10:12 , Marcel Loose wrote:
>
> >
> > On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
> >
> >>> Hi all,
> >>>
> >>> I was wondering how I could generate a list of user-definable
CMake
> >>> variables. This list, with
On 28. Sep, 2010, at 10:12 , Marcel Loose wrote:
>
> On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
>
>>> Hi all,
>>>
>>> I was wondering how I could generate a list of user-definable CMake
>>> variables. This list, with a brief help per variable, would be
> *very*
>>> useful for the end-user
2010/9/28 Marcel Loose :
>
> On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
>
>> > Hi all,
>> >
>> > I was wondering how I could generate a list of user-definable CMake
>> > variables. This list, with a brief help per variable, would be
> *very*
>> > useful for the end-user. It's a bit like the we
On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
> > Hi all,
> >
> > I was wondering how I could generate a list of user-definable CMake
> > variables. This list, with a brief help per variable, would be
*very*
> > useful for the end-user. It's a bit like the well-known "configure
> > --help" whi
On 28. Sep, 2010, at 9:33 , Marcel Loose wrote:
> Hi all,
>
> I was wondering how I could generate a list of user-definable CMake
> variables. This list, with a brief help per variable, would be *very*
> useful for the end-user. It's a bit like the well-known "configure
> --help" which gives you
Hi all,
I was wondering how I could generate a list of user-definable CMake
variables. This list, with a brief help per variable, would be *very*
useful for the end-user. It's a bit like the well-known "configure
--help" which gives you a overview of all variables that can be set.
Best regards,
M
32 matches
Mail list logo
