On 05/23/2011 08:42 PM, Sanatan Rai wrote:
> On 23 May 2011 17:46, Michael Hertling wrote:
>> In summary, this whole issue is not related to C++ or even to CMake,
>> but to the manner static libraries are handled: The linker - at least
>> the GNU one - picks out entire object files, or drops them
Sanatan Rai wrote:
> Unfortunately, I am stuck with the paradigm of having to kludge loading an
> entire library. For various reasons the one may not have a reference to
> the hosted object in main, which must remain agnostic. Indeed, in my
> particular line of business (finance), this happens to
On 23 May 2011 17:46, Michael Hertling wrote:
> On 05/23/2011 05:09 PM, Sanatan Rai wrote:
>> On 23 May 2011 16:00, Michael Wild wrote:
>>> Everything that relies on static/global initialization to register
>>> factories is an implicit scheme. An explicit scheme is where the
>>> dependent code (e
On 05/23/2011 05:09 PM, Sanatan Rai wrote:
> On 23 May 2011 16:00, Michael Wild wrote:
>> Everything that relies on static/global initialization to register
>> factories is an implicit scheme. An explicit scheme is where the
>> dependent code (e.g. the main() function) calls a function to do the
>
On 05/23/2011 05:09 PM, Sanatan Rai wrote:
> On 23 May 2011 16:00, Michael Wild wrote:
>> Everything that relies on static/global initialization to register
>> factories is an implicit scheme. An explicit scheme is where the
>> dependent code (e.g. the main() function) calls a function to do the
>
On Mon, May 23, 2011 at 10:51 AM, Sanatan Rai wrote:
> On 23 May 2011 15:11, Michael Wild wrote:
> >>> Yes, but you are registering the concrete factories implicitly instead
> >>> of explicitly, which is causing you the trouble you experience.
> >>>
> >>> Better have your user provide a function
On May 23, 2011, at 11:09 AM, Sanatan Rai wrote:
> On 23 May 2011 16:00, Michael Wild wrote:
>> Everything that relies on static/global initialization to register
>> factories is an implicit scheme. An explicit scheme is where the
>> dependent code (e.g. the main() function) calls a function to
On 23 May 2011 16:00, Michael Wild wrote:
> Everything that relies on static/global initialization to register
> factories is an implicit scheme. An explicit scheme is where the
> dependent code (e.g. the main() function) calls a function to do the
> registration.
Ok, got you. However, would t
On 05/23/2011 04:51 PM, Sanatan Rai wrote:
> On 23 May 2011 15:11, Michael Wild wrote:
Yes, but you are registering the concrete factories implicitly instead
of explicitly, which is causing you the trouble you experience.
Better have your user provide a function registering his
On 23 May 2011 15:11, Michael Wild wrote:
>>> Yes, but you are registering the concrete factories implicitly instead
>>> of explicitly, which is causing you the trouble you experience.
>>>
>>> Better have your user provide a function registering his/her classes
>>> explicitly.
>>
>> I guess this i
>-Original Message-
>From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Michael Wild
>Sent: Monday, May 23, 2011 9:12 AM
>To: cmake@cmake.org
>Subject: Re: [CMake] Newbie question: Static linking
>
>On 05/23/2011 03:25 PM, Sanatan Rai wrote:
&g
On 05/23/2011 04:40 PM, aaron.mead...@thomsonreuters.com wrote:
>> -Original Message-
>> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
> Behalf Of Michael Wild
>> Sent: Monday, May 23, 2011 9:12 AM
>> To: cmake@cmake.org
>> Subject: Re
On May 23, 2011, at 10:11 AM, Michael Wild wrote:
> On 05/23/2011 03:25 PM, Sanatan Rai wrote:
>> On 23 May 2011 13:38, Michael Wild wrote:
>>> On 05/23/2011 02:20 PM, Sanatan Rai wrote:
On 23 May 2011 12:54, Michael Jackson wrote:
> You might want to take a look at the Factory design p
On 05/23/2011 03:25 PM, Sanatan Rai wrote:
> On 23 May 2011 13:38, Michael Wild wrote:
>> On 05/23/2011 02:20 PM, Sanatan Rai wrote:
>>> On 23 May 2011 12:54, Michael Jackson wrote:
You might want to take a look at the Factory design pattern.
>>>
>>> That's exactly what I use...
>>>
>>>
On 23 May 2011 13:38, Michael Wild wrote:
> On 05/23/2011 02:20 PM, Sanatan Rai wrote:
>> On 23 May 2011 12:54, Michael Jackson wrote:
>>> You might want to take a look at the Factory design pattern.
>>>
>>
>> That's exactly what I use...
>>
>> --Sanatan
>
> Yes, but you are registering the concr
On 05/23/2011 02:20 PM, Sanatan Rai wrote:
> On 23 May 2011 12:54, Michael Jackson wrote:
>> You might want to take a look at the Factory design pattern.
>>
>
> That's exactly what I use...
>
> --Sanatan
Yes, but you are registering the concrete factories implicitly instead
of explicitly, which
On 23 May 2011 12:54, Michael Jackson wrote:
> You might want to take a look at the Factory design pattern.
>
That's exactly what I use...
--Sanatan
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/ope
You might want to take a look at the Factory design pattern.
-
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
Sent from my mobile device.
On May 23, 2011, at 5:51, Sanatan Rai wr
On 23 May 2011 10:18, Michael Wild wrote:
> On 05/23/2011 10:23 AM, Hendrik Sattler wrote:
>> Zitat von Sanatan Rai :
>>> The `global initialisation' stuff is just the following pattern:
>>>
>>> namespace {
>>> helper1 *helper1Creator()
>>> {
>>> return (new helper1());
>>> }
>>> const
On 05/23/2011 10:23 AM, Hendrik Sattler wrote:
> Zitat von Sanatan Rai :
>> The `global initialisation' stuff is just the following pattern:
>>
>> namespace {
>> helper1 *helper1Creator()
>> {
>> return (new helper1());
>> }
>> const bool helper1Registered = factory::instance().register
Zitat von Sanatan Rai :
The `global initialisation' stuff is just the following pattern:
namespace {
helper1 *helper1Creator()
{
return (new helper1());
}
const bool helper1Registered = factory::instance().registerhelper
("helper1", helper1Creator);
}
So when I put the helpers i
On 23 May 2011 00:53, Hendrik Sattler wrote:
> Am Montag, 23. Mai 2011, 01:36:14 schrieb Sanatan Rai:
>> After cmake, and make all, the libraries build as static archives, ie I get
>> liblib1.a, liblib2.a, libhelper1.a, libhelper2.a and executable myProj in
>> the appropriate locations. However, t
Am Montag, 23. Mai 2011, 01:36:14 schrieb Sanatan Rai:
> After cmake, and make all, the libraries build as static archives, ie I get
> liblib1.a, liblib2.a, libhelper1.a, libhelper2.a and executable myProj in
> the appropriate locations. However, the executable myProj does not appear
> to have link
Hi folks,
This has probably been done to death before, so apologies
in advance.
I have a project wherein I want all the project libraries to be linked
statically to the final executables.
I certainly get static libraries when I run make, however, two of
the libraries don't seem to link s
1. cmake:mex problem
According to the webpage (http://www.cmake.org/Wiki/CMake:MatlabMex)
we can tell CMake (patched version) to treat the mex build script as the
project's compiler which can be done by the command (CC=mex CXX=mex cmake
/path/to/project/source).
For the examples they provided, it h
On Friday 24 September 2010, David Aldrich wrote:
> Hi
>
> Surely been asked before, but may I ask:
>
> Does the cmake dependency generator operate when cmake is invoked or when
> make is subsequently invoked?
It is invoked during the make run.
> Does it use a traditional method such as makedepen
Hi
Surely been asked before, but may I ask:
Does the cmake dependency generator operate when cmake is invoked or when make
is subsequently invoked?
Does it use a traditional method such as makedepend or is it unique to cmake?
Thanks
David
___
Powere
the same
things I have.
moving along slowly, it is taking longer than I thought to do this cmake
porting test, but...
--
From: "Michael Hertling"
Sent: Thursday, May 27, 2010 10:16 PM
To:
Subject: Re: [CMake] newbie question - what t
2010/5/28 Michael Hertling :
> On 05/28/2010 12:14 AM, Doug Reiland wrote:
>> okay, I have ordered the book. But, in the meantime.
>>
>> I am continuing to port a large library from in-house build to cmake
>> for evaluation.
>> What builtin targets are supported?
>
> On *nix, run CMake on a directo
On 05/28/2010 12:14 AM, Doug Reiland wrote:
> okay, I have ordered the book. But, in the meantime.
>
> I am continuing to port a large library from in-house build to cmake
> for evaluation.
> What builtin targets are supported?
On *nix, run CMake on a directory with an empty CMakeLists.txt, then
okay, I have ordered the book. But, in the meantime.
I am continuing to port a large library from in-house build to cmake
for evaluation.
What builtin targets are supported?
I got lex, gperf, and other kinds of stuff.
A (pseudo code) didn't work:
add_library(foo *.c *.gpref)
thanks!
___
Hi Arjen
> this is PLplot-specific, has nothing (or at least very little) to do
> with CMake. The problem is that the program that creates these driver
> files needs a few DLLs and they are not yet in the DLL subdirectory.
Sorry, I will try your suggestion and move back to the PLplot mail list.
Hi David,
this is PLplot-specific, has nothing (or at least very little) to do
with CMake. The problem is that the program that creates these driver
files needs a few DLLs and they are not yet in the DLL subdirectory.
Can you check with DependencyWalker or similar programs what DLLs
are missing?
Hi Arjen
> you should start cmake in a clean directory - old stuff might get in the
> way otherwise, as a lot of information is being cached.
Yes, that was the problem. Thanks.
As I wrote in another mail this morning (the order seems to have got reversed)
CMake now succeeds but nmake fails:
[
Hi David,
you should start cmake in a clean directory - old stuff might get in the
way otherwise, as a lot of information is being cached.
Regards,
Arjen
On 2009-09-10 10:05, David Aldrich wrote:
Hi Bill and Alan
Thank you both very much for answering my question. I did indeed have an old ve
Hi Bill and Alan
Thank you both very much for answering my question. I did indeed have an old
version of CMake, from a forgotten installation of Cygwin, and that was being
invoked. I have now deleted that old CMake (and hopefully Cygwin as well) and
am now truly running 2.6.4.
C:\plplot-5.9.5
Hi
> Any idea why this is happening please?
Sorry, I should have thought a little more. I deleted the contents of
buildnmake and now CMake succeeds.
I then executed:
C:\plplot-5.9.5\buildnmake>path=...\plplot-5.9.5\buildnmake\dll;%PATH%
C:\plplot-5.9.5\buildnmake>nmake
and the nmake output t
David Aldrich wrote:
Hi
I am new to cmake. I have installed cmake (using
cmake-2.6.4-win32-x86.exe) on my Win XP platform, on which I also have
Visual Studio 2005 Prof and Visual Studio 2008 Express installed.
I am trying to build PLplot, whose instructions tell me to run:
cmake -G "NMake
Hi
I am new to cmake. I have installed cmake (using cmake-2.6.4-win32-x86.exe) on
my Win XP platform, on which I also have Visual Studio 2005 Prof and Visual
Studio 2008 Express installed.
I am trying to build PLplot, whose instructions tell me to run:
cmake -G "NMake Makefiles" -DCMAKE_INSTAL
Hi
I am new to cmake. I have installed cmake (using cmake-2.6.4-win32-x86.exe) on
my Win XP platform, on which I also have Visual Studio 2005 Prof and Visual
Studio 2008 Express installed.
I am trying to build PLplot, whose instructions tell me to run:
cmake -G "NMake Makefiles" -DCMAKE_INSTAL
Hi Joachim,
BTW, is there a *searchable* archive of the mailing list archived at
http://www.cmake.org/pipermail/cmake/
?
http://www.mail-archive.com/cmake@cmake.org/
Regards,
Werner
Greetings,
joachim
___
CMake mailing list
CMake@cmake.org
http:/
Hello list,
am I correct in the following use of the CMake cache:
Suppose that in your source code, a preprocessor macro
#if defined(USE_MEMSET)
...
#elif defined(USE_BZERO)
...
#endif
decides on whether you want to use the function memset() or bzero() to
set the first n bytes of a byte area to
On Wed, Sep 24, 2008 at 5:11 AM, Roy Zuo <[EMAIL PROTECTED]> wrote:
> Thanks a lot, and list(REMOVE_ITEM ...) works well for me.
>
> Another stupid question, as I am really new to c++. There are some cpp
> files containing only inline functions and some template class
> functions. The could not be
Thanks a lot, and list(REMOVE_ITEM ...) works well for me.
Another stupid question, as I am really new to c++. There are some cpp
files containing only inline functions and some template class
functions. The could not be compiled correctly as well, but if I
exclude them from compilation, errors wi
On Mon, Sep 22, 2008 at 10:00 AM, Roy Zuo <[EMAIL PROTECTED]> wrote:
> Hello eveyone,
>
> I am just new to cmake and have some trouble when compiling a big
> project whose cpp source files are put deep inside subdirectories.
>
> In my CMakeLists.txt, I use AUX_SOURCE_DIRECTORY(subdir VARX) and
> S
Hello eveyone,
I am just new to cmake and have some trouble when compiling a big
project whose cpp source files are put deep inside subdirectories.
In my CMakeLists.txt, I use AUX_SOURCE_DIRECTORY(subdir VARX) and
SET(SRC ${VAR1} ${VAR2} ...) to put all the source files in a
variable, and then u
On Jan 15, 2008 4:34 AM, Tang Jacky <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I have an open source library that does not come with cmake.
> But I would like to use it as if it is a package so as to combine with my
> own cmake project.
> Is it easy or difficult?
> What would people usually do to c
Dear all,
I have an open source library that does not come with cmake.
But I would like to use it as if it is a package so as to combine with my
own cmake project.
Is it easy or difficult?
What would people usually do to combine cmake with non-cmake libraries?
Regards
Bunny
__
On 2008-01-11 08:05+1100 Pacesie wrote:
If I want to generate document files as part of the build, should I first
create an ADD_CUSTOM_TARGET then have it depends on the generated files
defined by ADD_CUSTOM_COMMAND? ( It would be nice if file generation can be
defined as a target so the extra s
On Jan 10, 2008 11:50 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> Pacesie wrote:
> > Hello,
> >
> > In my C++ program I want to auto-generate a header ( .h ) file, which is
> > included in most sources. I use ADD_CUSTOM_COMMAND to generate it, but I
> > don't know how to neatly write the depende
Pacesie wrote:
Hello,
In my C++ program I want to auto-generate a header ( .h ) file, which is
included in most sources. I use ADD_CUSTOM_COMMAND to generate it, but I
don't know how to neatly write the dependency to it.
Add the .h file as a source file of the target that uses it.
-Bill
_
Hello,
In my C++ program I want to auto-generate a header ( .h ) file, which is
included in most sources. I use ADD_CUSTOM_COMMAND to generate it, but I
don't know how to neatly write the dependency to it.
I could use ADD_DEPENDENCY to add the generated header to all final targets,
but it will ge
Hi,
> Now, I've got it to build the exe in the "bin" folder, but Visual Studio
> is being annoying by building it in "bin/debug". I've already tried
> "set(CMAKE_BUILD_TYPE Release)" but that doesn't remove the debug
> folder. Thanks.
Someone here on the mailing list mentioned a workaround fo
Thanks a ton for the help so far.
Now, I've got it to build the exe in the "bin" folder, but Visual Studio
is being annoying by building it in "bin/debug". I've already tried
"set(CMAKE_BUILD_TYPE Release)" but that doesn't remove the debug
folder. Thanks.
Am Montag 03 September 2007 00:12 schrieb Jack Kelly:
> Pingu wrote:
> > All I'm asking for is a way to tell the compiler (VS8) to build the exe
> > in a certain folder as opposed to the build folder where the project
> > files are located. It really doesn't seem like it'd be that hard, but I
> > r
Pingu wrote:
All I'm asking for is a way to tell the compiler (VS8) to build the exe
in a certain folder as opposed to the build folder where the project
files are located. It really doesn't seem like it'd be that hard, but I
really don't understand CMake all that well right now.
You should b
An experienced friend of mine suggested getting CMake going on this
project I was starting at the time. Naturally, I had never heard of it
and he spend most of his time setting up the system. He left he group
recently and I'm a bit lost at how to do even simple things. A little
bit of help woul
Christian Convey wrote:
I've got two subprojects: A library FOO, and a program BAR.
If I have this:
ADD_EXECUTABLE(BAR main.cpp)
TARGET_LINK_LIBRARIES(BAR FOO)
Then does CMake somehow realize that it needs to build its FOO library
before trying to link the BAR program?
Yes. TARGET_LINK_LIBR
I've got two subprojects: A library FOO, and a program BAR.
If I have this:
ADD_EXECUTABLE(BAR main.cpp)
TARGET_LINK_LIBRARIES(BAR FOO)
Then does CMake somehow realize that it needs to build its FOO library
before trying to link the BAR program?
Or do I need to explicitly tell it to do this, us
Kevin Tucker wrote:
Path names with spaces seems to be a hard problem. There's a bug posted
for this same problem with Microsoft's nmake:
http://www.itk.org/Bug/bug.php?op=show&bugid=3&pos=1 and it's marked
"Won't Fix". No notes as to why that decision was made...
I need to figure a way around
ed to figure a way around this as well...
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Convey
Sent: Sunday, February 25, 2007 12:22 PM
To: cmake@cmake.org
Subject: [CMake] Newbie question
Thanks Alan.
I went ahead an broke my project into
Thanks Alan.
I went ahead an broke my project into a top-level CMake file, plus one
for a subdirectory containing library code, and one for a subdirectory
containing library-demo code.
That seems to work so far, EXCEPT: when the path to the subdirectory
includes a directory with a space in the
On 2007-02-25 13:34-0500 Christian Convey wrote:
(Couldn't spot this in the docs - sorry if it's obvious...)
I've got a project that involves a library, and several demo apps that
use that library.
- Is there a strong reason to avoid using a single CMake file to
express the logic for building
(Couldn't spot this in the docs - sorry if it's obvious...)
I've got a project that involves a library, and several demo apps that
use that library.
- Is there a strong reason to avoid using a single CMake file to
express the logic for building the library and the apps?
- How do I express the f
ucker
Cc: CMake Mailing List
Subject: Re: [CMake] Newbie question
Hi Kevin,
The problem comes from the `PROJECT' command: put some quotes on the
project name otherwise CMake understands that you want to use the
language `Prog' on a new project named `Test'. That is why CMake is
try
Hi Kevin,
The problem comes from the `PROJECT' command: put some quotes on the
project name otherwise CMake understands that you want to use the
language `Prog' on a new project named `Test'. That is why CMake is
trying to open the file CMakeProgCompiler.cmake as there are
`CMakeJavaCompiler.cmak
I've been doing a lot of reading and yet, I don't seem to be able to get
even the simplest project to work. I tried searching the cmake list
archives, but couldn't find anything helpful.
I'm on Win2k3 and cmake 2.4.6(used the windows installer) and visual
studio .NET 2003.
My test.c file i
At 09:06 PM 6/1/2006, Bennett Smith wrote:
>Hello,
>
>I am trying to convert our current home-brew build system to use
>cmake. One issue we have is that some libraries are built using
>Visual C++ 7.1 and other libraries and executables are built using
>VIsual C++ 6.0. I would like to somehow indic
Hello,
I am trying to convert our current home-brew build system to use
cmake. One issue we have is that some libraries are built using
Visual C++ 7.1 and other libraries and executables are built using
VIsual C++ 6.0. I would like to somehow indicate in each subdirectory
which version of the C+
69 matches
Mail list logo
