Hi David/Bill,
I removed the extra set of . I am not sure how they came into :-(
But, still the problem persists, following is the output:
C:\Work\PCT_LTE\Hercules\CID\MapperGenerator\build_nmakecmake ../
-GNMake Makefiles --trace
Running with trace output on.
Hi all,
I've been struggling with this for hours now and I can't seem to get a
grip on it.
I have a header file that must be (re)generated during 'make' when some
external data have changed. I can successfully generate this file during
'cmake' using configure_file(), but I haven't been able to
I do a similar thing with an XSD file from which I generate c++ wrapper classes
for accessing the corresponding XML
Note the DEPENDS line !
MACRO(XSD FILE NAMESPACE)
ADD_CUSTOM_COMMAND(
OUTPUT ${CMAKE_CURRENT_SOURCE_DIR}/xml/${FILE}.cpp
OUTPUT
Hi Jack,
The difference with your and my case is that you have an input file
(the .xsd file) and output files (the .h and .cpp files). In my case I
generate the output file, e.g. myheader.h, from myheader.h.in, using
configure_file(). The problem is that I cannot get this to work during
'make',
On 15. Jan, 2010, at 16:25 , Marcel Loose wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On Fri, Jan 15, 2010 at 9:44 AM, Marcel Loose lo...@astron.nl wrote:
Hi Jack,
The difference with your and my case is that you have an input
file
(the .xsd
On Fri, Jan 15, 2010 at 10:25 AM, Marcel Loose lo...@astron.nl wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On Fri, Jan 15, 2010 at 9:44 AM, Marcel Loose lo...@astron.nl wrote:
Hi Jack,
The difference with your and my case is that you have an input
On Fri, Jan 15, 2010 at 10:35 AM, Michael Wild them...@gmail.com wrote:
On 15. Jan, 2010, at 16:25 , Marcel Loose wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On Fri, Jan 15, 2010 at 9:44 AM, Marcel Loose lo...@astron.nl wrote:
Hi Jack,
The difference
On 15. Jan, 2010, at 16:38 , David Cole wrote:
On Fri, Jan 15, 2010 at 10:35 AM, Michael Wild them...@gmail.com wrote:
On 15. Jan, 2010, at 16:25 , Marcel Loose wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On Fri, Jan 15, 2010 at 9:44 AM, Marcel Loose lo...@astron.nl
On Fri, 2010-01-15 at 16:35 +0100, Michael Wild wrote:
On 15. Jan, 2010, at 16:25 , Marcel Loose wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On Fri, Jan 15, 2010 at 9:44 AM, Marcel Loose lo...@astron.nl
wrote:
Hi Jack,
The difference with your and my
On Jan 13, 2010, at 4:58 PM, Andreas Pakulat wrote:
On 13.01.10 13:34:34, clin...@elemtech.com wrote:
I've also seen people put a qt.conf file in the Qt installation, to
override the compiled-in paths.
That's probably how its done by the Windows installer.
Thats one way to do it, but
Indeed, it is much more sophisticated, so it may be more bugged ;-)
shell i send you my scripts to take a look?
It's not necessary. I have downloaded the refactoring branch of yars.
Thanks.
I comment my OCaml scripts and I send you, so that you could also have a
look.
I have took a look at
hi,
Indeed, it is much more sophisticated, so it may be more bugged ;-)
i can help debugging :)
shell i send you my scripts to take a look?
It's not necessary. I have downloaded the refactoring branch of yars. Thanks.
oh, ok, then you should have the newest version (last yars revision is
On Fri, 2010-01-15 at 16:45 +0100, Michael Wild wrote:
On 15. Jan, 2010, at 16:38 , David Cole wrote:
On Fri, Jan 15, 2010 at 10:35 AM, Michael Wild them...@gmail.com
wrote:
On 15. Jan, 2010, at 16:25 , Marcel Loose wrote:
On Fri, 2010-01-15 at 10:07 -0500, David Cole wrote:
On
Reported as bug #10151.
Steve
On Thu, Jan 14, 2010 at 5:57 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
Steven Wilson wrote:
The mechanism that creates the ReRunCMake.make file seems to not correctly
gather all the dependent CMakeLists.txt files from a project. For example
if you have
On Sun, Jan 10, 2010 at 3:50 PM, Luke Parkinson lparkin...@vpac.org wrote:
- James Bigler jamesbig...@gmail.com wrote:
On Thu, Jan 7, 2010 at 8:52 PM, Luke Parkinson lparkin...@vpac.org
wrote:
- James Bigler jamesbig...@gmail.com wrote:
On Wed, Jan 6, 2010 at 11:00 PM,
On Friday 08 January 2010, Ryan Pavlik wrote:
On Thu, Jan 7, 2010 at 4:00 PM, Jed Brown j...@59a2.org wrote:
On Thu, 07 Jan 2010 15:54:33 -0600, Ryan Pavlik rpav...@iastate.edu
wrote:
If you use the _LIBRARIES variable, you don't need to even mess around
with the imported targets
I have an existing large hierarchically structured code base, but I want
to extract a cut-down source code tree that only contains the source
code files necessary for a particular project. The files I don't want
are scattered through-out the code tree.
I want to be able to extract this
I think you just change the appropriate flag in
CMAKE_CXX_FLAGS_Config_Type variable to control this. By Default It uses
the Dll runtime via the MD/MDd flags.
See this table for the other variations of this flag.
http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.71).aspx
On Fri, Jan 15, 2010
While I can build shared libraries written in C or C++ using CMAKE 2.8
without any problems on Visual Studio, I am having problems building
shared libraries on Vista 64 using the Intel 11 FORTRAN compiler.
What is the best practice to build DLLs on Windows using FORTRAN?
Thanks,
Jody
On Fri, Jan 15, 2010 at 05:57:20PM +, Ian Scott wrote:
I have an existing large hierarchically structured code base, but I want
to extract a cut-down source code tree that only contains the source
code files necessary for a particular project. The files I don't want
are scattered
On 15.01.10 11:02:53, Michael Jackson wrote:
On Jan 13, 2010, at 4:58 PM, Andreas Pakulat wrote:
On 13.01.10 13:34:34, clin...@elemtech.com wrote:
I've also seen people put a qt.conf file in the Qt installation,
to override the compiled-in paths.
That's probably how its done by the
On Jan 15, 2010, at 2:17 PM, Tyler Roscoe wrote:
On Fri, Jan 15, 2010 at 05:57:20PM +, Ian Scott wrote:
I have an existing large hierarchically structured code base, but I
want
to extract a cut-down source code tree that only contains the source
code files necessary for a particular
Chauhan, Vikas wrote:
Hi David/Bill,
I removed the extra set of “”. I am not sure how they came into L
Can you try this:
1. Create a new directory:
mkdir foo
2. Create a CMakeLists.txt file in foo
project(foo)
add_library(foo bar.c)
Create an empty file bar.c.
3. Create a build
Hi!
This proposal addresses the following issue:
currently there is no solution for creating Visual Studio project
files for static runtime without editing the cmake files.
As the goal of cmake is to define a project in an abstract way it should
be possible to generate for static runtime only
It can already be done from the command line by setting the CMAKE_CXX_FLAGS*
variables with the -D argument to cmake.
You can also do this from within the CMakeLists.txt files.
Clint
On Friday 15 January 2010 01:20:26 pm Jochen Wilhelmy wrote:
Hi!
This proposal addresses the following
Please see it from the point of view of someone who is not a cmake
expert and also not a visual studio expert.
such a user will not know what CMAKE_CXX_FLAGS are
and also not know that /MD or /MT controls dynamic or
static runtime of cl.exe on the command line
(and what about the settings in the
For your project you can always add your own flags such as:
CMakeLists.txt Begin
if (VS_USE_STATIC_RUNTIME)
set (CMAKE_CXX_FLAGS .)
endif()
CMakeLists.txt-- END
Then on the command line do the following:
cmake -G Visual Studio 9 2008 -DVS_USE_STATIC_RUNTIME=ON ../
or from a
Hi!
thanks for the reply, but it has two drawbacks:
1. it needs to change CMakeLists.txt which I don't want to
(as written in my proposal) since it is not my project but a
large open source project. It gets developed mainly on unix
and macos but since it uses cmake I can compile it for
windows
Can you try this:
1. Create a new directory:
mkdir foo
2. Create a CMakeLists.txt file in foo
project(foo)
add_library(foo bar.c)
Create an empty file bar.c.
3. Create a build directory under foo:
mkdir build
4. run cmake
cd build
cmake -GNMake Makefiles ..
Great, it
Chauhan, Vikas wrote:
Can you try this:
1. Create a new directory:
mkdir foo
2. Create a CMakeLists.txt file in foo
project(foo)
add_library(foo bar.c)
Create an empty file bar.c.
3. Create a build directory under foo:
mkdir build
4. run cmake
cd build
cmake -GNMake Makefiles ..
Great,
Remove this CMakeCache.txt file, and re-run and it should work.
I would start with a clean build tree and source tree. If you have
ever run cmake in-source, clean your source tree so that it has no
generated stuff in it. Also, remove the entire build tree, then you
should be fine.
The PLplot project has been supporting some additional Fortran compilers via
files in cmake/modules/Platform in our source tree where we use
set(CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/cmake/modules)
This CMake_MODULE_PATH approach requires that we put a slightly modified
version of
Site: infinitron
Build name: Linux64_Release_gfortran
Determine Nightly Start Time
Specified time: 00:00:00 PST
Create new tag: 20100115-0800 - Nightly
Updating the repository
Updating the repository:
/global_scratch/regress/acurosbv/Release_gcc432_gfortran/source
Use SVN repository
On Fri, Jan 15, 2010 at 3:20 PM, Jochen Wilhelmy j.wilhe...@arcor.de wrote:
Hi!
This proposal addresses the following issue:
currently there is no solution for creating Visual Studio project
files for static runtime without editing the cmake files.
As the goal of cmake is to define a project
On Fri, Jan 15, 2010 at 1:21 PM, Dave Partyka dave.part...@kitware.com wrote:
I think you just change the appropriate flag in
CMAKE_CXX_FLAGS_Config_Type variable to control this. By Default It uses
the Dll runtime via the MD/MDd flags.
See this table for the other variations of this flag.
35 matches
Mail list logo
