Am Mittwoch, 17. November 2010 schrieb James Bigler:
> Has anyone else noticed situations where VS puts the first project (as
> determined alphabetically) in a project folder as the last project?
Yes, I have seen this when using the new FOLDER property for targets. I see
this behaviour within the
On 11/13/2010 03:08 PM, Marcus D. Hanwell wrote:
> On Nov 13, 2010, at 8:57 AM, Michael Hertling wrote:
>
>> On 11/12/2010 02:13 PM, Hector Martinez-Seara wrote:
>>> Dear all,
>>> I'm trying to install openbabel in linux which in its last version
>>> (2.3.0) uses cmake installer. I haven't been ab
On Tue, Nov 16, 2010 at 10:15:28PM -0500, David Doria wrote:
> Is the goal simply to copy
> ...VTK/bin/libvtkHybrid.a
> into the package?
>
> I tried this:
> INSTALL(CODE "\${VTK_DIR}/bin/libvtkHybrid.a")
More like:
INSTALL(FILES "${VTK_DIR}/bin/libvtkHybrid.a")
tyler
___
Is the goal simply to copy
...VTK/bin/libvtkHybrid.a
into the package?
I tried this:
INSTALL(CODE "\${VTK_DIR}/bin/libvtkHybrid.a")
But I get:
Parse error. Expected a command name, got unquoted argument with text
"${VTK_DIR}/bin/libvtkHybrid.a".
I made a home for this here:
http://www.vtk.org/
> Also use VS IDE to make sure the library is listed.
The library is indeed listed in "Additional Dependencies" of the
linker for the executable target.
> What symbols? Try running dumpbin /symbols OSC.lib.
I figured it out - I had to link to "winmm" to get the symbol:
symbol __imp__timeGetTime
On 11/16/2010 7:19 PM, David Doria wrote:
Hm, it works correctly in Linux, but I still get a bunch of
error LNK2019: unresolved external symbol
What symbols?
Try running dumpbin /symbols OSC.lib. Also use VS IDE to make sure the
library is listed.
Everything look ok? Any thoughts?
Looks
Hm, it works correctly in Linux, but I still get a bunch of
error LNK2019: unresolved external symbol
errors in Windows.
The only difference I see is that the .lib file gets created in a
subdirectory of bin/
bin/Debug/OSC.lib (or bin/Release/OSC.lib)
vs the .a file which gets created in bin di
Has anyone else noticed situations where VS puts the first project (as
determined alphabetically) in a project folder as the last project?
CMakePredefinedTargets
-- PACKAGE
-- RUN_TESTS
-- ZERO_CHECK
-- INSTALL
I'm using VS 2008 SP 1 with CMake 2.8.3.
I've verified this with a simple project and
Michael Jackson said the following on 11/15/2010 11:56 AM:
Ahh. It is a bit clearer the tract you are taking. What I am
suggesting is that you only have to run the "scanner" once and keep
the results in CMake syntax files so that CMake can just simply re-use
the list. As you add headers during
On 11/16/2010 04:52 PM, Belcourt, K. Noel wrote:
>
> On Nov 16, 2010, at 2:50 PM, Brad King wrote:
>
>> On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote:
>>> which is the same list of libraries in these SUBDIRS commands in the
>>> top-level CMakeLists.txt file (in reverse order). There's a single
On Nov 16, 2010, at 2:48 PM, Eric Noulard wrote:
2010/11/16 Belcourt, K. Noel :
On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote:
On Nov 16, 2010, at 1:59 PM, Brad King wrote:
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying
On Nov 16, 2010, at 2:48 PM, Eric Noulard wrote:
2010/11/16 Belcourt, K. Noel :
On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote:
On Nov 16, 2010, at 1:59 PM, Brad King wrote:
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying
On Nov 16, 2010, at 2:50 PM, Brad King wrote:
On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote:
which is the same list of libraries in these SUBDIRS commands in the
top-level CMakeLists.txt file (in reverse order). There's a single
library in each of these subdirs of the same lower-cased name.
On 11/16/2010 04:24 PM, Belcourt, K. Noel wrote:
> which is the same list of libraries in these SUBDIRS commands in the
> top-level CMakeLists.txt file (in reverse order). There's a single
> library in each of these subdirs of the same lower-cased name.
>
> ...
> SUBDIRS(Modules)
> SUBDIRS(MP
2010/11/16 Belcourt, K. Noel :
>
> On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote:
>
>> On Nov 16, 2010, at 1:59 PM, Brad King wrote:
>>
>>> On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying to force
all the modules in th
On Nov 16, 2010, at 2:05 PM, Belcourt, K. Noel wrote:
On Nov 16, 2010, at 1:59 PM, Brad King wrote:
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying to force
all the modules in the project to build first so I created a single
library
On Nov 16, 2010, at 1:59 PM, Brad King wrote:
Hi Noel,
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
I've attached my project's top-level Makefile. I'm trying to force
all the modules in the project to build first so I created a single
library called modules that contains all my Fortran 90
Hi Noel,
On 11/16/2010 01:11 PM, K. Noel Belcourt wrote:
> I've attached my project's top-level Makefile. I'm trying to force
> all the modules in the project to build first so I created a single
> library called modules that contains all my Fortran 90 module files.
> I'm invoking the Make
On Tue, Nov 16, 2010 at 12:27 AM, Rolf Eike Beer wrote:
> Am Dienstag, 16. November 2010 schrieb Eric Noulard:
> > 2010/11/15 James Bigler
> >
> > > If I set a COMPILE_FLAGS property on a header file via
> > > set_source_files_properties, CMake decides that these header files now
> > > need to b
Be sure that you have
INCLUDE_DIRECTORIES( [path to Internal.h and External.h] )
set.
James
On Tue, Nov 16, 2010 at 12:24 PM, David Doria wrote:
> Ryan,
>
> The issue is that these headers are only used internally to this
> collection of files, so I don't want to have to include them in my
>
Ryan,
The issue is that these headers are only used internally to this
collection of files, so I don't want to have to include them in my
code. Here is a skeleton:
The files I've been given
--
External.h
External.cpp
Internal.h (used by External)
Internal.cpp
My files
MyCode
On Tue, Nov 16, 2010 at 2:06 PM, David Doria wrote:
> On Tue, Nov 16, 2010 at 1:35 PM, Michael Jackson
> wrote:
>> I think we used Qt as a basis because lots of people at the time were asking
>> for it. Probably the simplest to demonstrate would be an example that builds
>> a dynamic library and
If you have "unresolved external" errors, then you are (most likely)
missing a target_link_libraries call -- find out what library those
symbols are built into, and link to that library.
On Tue, Nov 16, 2010 at 2:03 PM, David Doria wrote:
> I am trying to use ADD_LIBRARY to create a .lib file fr
Is this a library that has built successfully before with another build
system? Has this application been built successfully before?
For instances where the actual implementation is in the .h file, you usually
must make sure you #include that header file in a cpp in your own
application (the app l
On Tue, Nov 16, 2010 at 1:35 PM, Michael Jackson
wrote:
> I think we used Qt as a basis because lots of people at the time were asking
> for it. Probably the simplest to demonstrate would be an example that builds
> a dynamic library and an executable that uses that library so therefor it
> must b
I am trying to use ADD_LIBRARY to create a .lib file from a collection
of .cpp and .h files.
If I do:
ADD_LIBRARY(LibraryName AllOfTheCPPFiles.cpp)
and then try to link against that library, I get many missing-function
type linker errors. I looked in the .h files and many of them have
actual func
Am Dienstag, 16. November 2010 schrieb luxInteg:
> Greetings,
>
> I am learning cmake.
>
>
> I have a fortran only project with some source files with f77 routines to
> compile, My CMakeLists.txt in the projects base directory has the
> following lines
>
> set(CMAKE_Fortran_COMPILER gfort
Greetings,
I am learning cmake.
I have a fortran only project with some source files with f77 routines to
compile, My CMakeLists.txt in the projects base directory has the following
lines
set(CMAKE_Fortran_COMPILER gfortran)
ENABLE_LANGUAGE(Fortran)
but running cmake ends li
I think we used Qt as a basis because lots of people at the time were
asking for it. Probably the simplest to demonstrate would be an
example that builds a dynamic library and an executable that uses that
library so therefor it must be packaged with the executable. Were you
wanting to write
Hi,
I've attached my project's top-level Makefile. I'm trying to force
all the modules in the project to build first so I created a single
library called modules that contains all my Fortran 90 module files.
I'm invoking the Makefile explicitly passing the modules as the
target to build
On 11/16/2010 06:18 PM, Andrea Galeazzi wrote:
> I'm trying to compile a static library named libkernel.a into a custom
> path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
> 1:
> set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
> "O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE}")
On 2010-11-16 09:35-0500 Torri, Stephen CIV NSWCDD, W15 wrote:
I am trying to merge a project that was using autoconf and GNUMakefiles. When
you use automake you can build static libraries in sub directories and then
link them together into one shared library in the end that was install. This
Am Dienstag, 16. November 2010 schrieb Andrea Galeazzi:
> I'm trying to compile a static library named libkernel.a into a custom
> path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
> 1:
> set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
> "O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_
I'm trying to compile a static library named libkernel.a into a custom
path. I tried to set ARCHIVE_OUTPUT_DIRECTORY in two ways:
1:
set_property(TARGET PROPERTY ARCHIVE_OUTPUT_DIRECTORY
"O:/kernel/${CMAKE_SYSTEM_NAME}/${CMAKE_BUILD_TYPE}")
message("library output: ${ARCHIVE_OUTPUT_DIRECTORY}")
2010/11/16 David Doria :
> Great, it's working. The only thing that was required was:
>
> SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "David Doria")
>
> Here is the working example:
> http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB
>
> The page you sent
> (http://www.vtk.org/Wiki/CMake:CPackPacka
You really can't, unfortunately because only one configuration is possible
per CMake build directory with the Makefile generator. Most people set
CMAKE_BUILD_TYPE to Debug when using the Eclipse CDT4 Generator so they can
debug.
If you need to test regularly with release binaries, one solution is
Hi all,
I found the Qt example here:
http://www.itk.org/Wiki/BundleUtilitiesExample
http://www.itk.org/Wiki/images/2/25/QtTest-Package-Example.zip
The two INSTALL commands seem fairly complicated - is there not a way
to do all of that in the project-to-be-included's cmake configuration
so that a
Great, it's working. The only thing that was required was:
SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "David Doria")
Here is the working example:
http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB
The page you sent
(http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX_only.29)
has a
I followed the tutorial at
http://www.cmake.org/Wiki/Eclipse_CDT4_Generator in order to generate an
Eclipse project.
The only difference is that I select eclipseCDT - MiinGW Makefiles
instead of eclipseCDT -Unix Makefiles".
What I don't understand is how can I manage multiple configurations in
On 11/15/2010 06:41 PM, Marek Szuba wrote:
> On Mon, 15 Nov 2010 12:00:04 -0500
> cmake-requ...@cmake.org wrote:
>
>> How do you select which of the libraries to use? Based on your
>> Fortran compiler?
> To be exact, based on the Fortran compiler used to build the
> binary-only library.
>
>> If s
40 matches
Mail list logo
