2008/1/16, Filipe Sousa <[EMAIL PROTECTED]>:
> Ted Berg wrote:
> > Filipe Sousa wrote:
> >
> > I aplogize, my initial post wasn't terribly clear. I'm currently
> > generating, for example, the following packages:
> >
> > foo-sdk-1.0.0.zip
> > foo-qa-tools-1.0.0.zip
> > foo-killer-app-1.0.0.zip
> >
2008/1/17, Hendrik Sattler <[EMAIL PROTECTED]>:
> Am Mittwoch 16 Januar 2008 schrieb Rodolfo Lima:
> > Well, if the above setup is made, one might call:
> > CC="i686-pc-linux-gnu-gcc" cmake . and it'll work, but this is
> > suboptimal IMHO. I can't see any other bad side effect of using the
> > com
Am Mittwoch 16 Januar 2008 schrieb Rodolfo Lima:
> Well, if the above setup is made, one might call:
> CC="i686-pc-linux-gnu-gcc" cmake . and it'll work, but this is
> suboptimal IMHO. I can't see any other bad side effect of using the
> complete compiler name instead of the short one.
gcc _is_ th
Iker Arizmendi wrote:
I've run into some trouble with how CMake 2.4.2 (and perhaps
later) handles the string "$ORIGIN" when it appears as part of
an RPATH. I've gotten around the trouble (see below), but would
appreciate any pointers on the correct way to use "$ORIGIN".
...
SET(CMAKE_INSTALL
Ted Berg wrote:
> Filipe Sousa wrote:
>
> I aplogize, my initial post wasn't terribly clear. I'm currently
> generating, for example, the following packages:
>
> foo-sdk-1.0.0.zip
> foo-qa-tools-1.0.0.zip
> foo-killer-app-1.0.0.zip
>
> These packages have different content and are targeted at
Eric Noulard escreveu:
> Could you explain a little more
> 0) Which version of CMake do you use?
cmake-cvs as of 2008/01/16
> 1) How did you invoke CMake with distcc?
>
> Is it something like:
> CC="distcc gcc" CXX="distcc g++" cmake
> or something different?
usually there's a direct
Ted Berg wrote:
> I have a body of source code that I am building with CMake, and I am
> interested in using CPack for packaging. The project currently
> generates 5 packages during the course of a build. I might be able to
> reduce that to 3, but it is unlikely to go lower.
>
> Can CPack do
2008/1/16, Rodolfo Lima <[EMAIL PROTECTED]>:
> Hi, I've been using distcc to be able to use a compiler farm here at
> work. There are a bunch of linux boxes, some are i686-pc-linux-gnu,
> others i386-pc-linux-gnu, x86_64-pc-linux-gnu, etc.
>
> The problem is that normally cmake chooses /usr/bin/gcc
Hi, I've been using distcc to be able to use a compiler farm here at
work. There are a bunch of linux boxes, some are i686-pc-linux-gnu,
others i386-pc-linux-gnu, x86_64-pc-linux-gnu, etc.
The problem is that normally cmake chooses /usr/bin/gcc as the compiler.
Once it gets chosen, distcc invokes
On 16.01.08 12:25:53, Andreas Schneider wrote:
> Andreas Pakulat wrote:
> > does anybody know of a "built-in" way of determining the c++ compiler
> > version? Specifically for GNU gcc?
> >
> > Or do I have to run CMAKE_CXX_COMPILER with --version and extract the
> > information myself?
>
> http:/
I've run into some trouble with how CMake 2.4.2 (and perhaps
later) handles the string "$ORIGIN" when it appears as part of
an RPATH. I've gotten around the trouble (see below), but would
appreciate any pointers on the correct way to use "$ORIGIN".
Regards,
Iker
Briefly, the problem seems to be
I have a body of source code that I am building with CMake, and I am
interested in using CPack for packaging. The project currently
generates 5 packages during the course of a build. I might be able to
reduce that to 3, but it is unlikely to go lower.
Can CPack do this in one pass? My initi
On Jan 16, 2008, at 2:05 PM, Leopold Palomo-Avellaneda wrote:
I have it .
target_link_libraries(${plugin} bulmalib ${QT_LIBRARIES} $
{PGSQL_LIBRARIES})
I think you either need more libraries in the above statement or
you are not compiling enough source files into the bulmalib library.
On Jan 16, 2008 2:28 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> wrote:
> I think that you rock it. And Benjamin you confirmed it. I suppose that if I
> define the classes as extern will not solve the problem, no?
If you link with "-undefined dynamic_lookup" I think it should work,
although
You could use the same technique found in VTK/Rendering/vtkTesting.cxx. Grep
for DartMeasurement and mimic what VTK does when one of its tests results in
a DifferenceImage.
Anything listed as a DartMeasurement in xml form in your test's output gets
transformed to appropriate entries in Test.xml.
A Dimecres 16 Gener 2008, Benjamin Reed va escriure:
> On Jan 16, 2008 2:11 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
> > I think that is your problem. If you plugin is ONLY linking against
> > bulmalib BUT aplinteligentesview is defined in bulmacont executable,
> > then the linking for the plugi
Hello,
How can I customize Test.xml generated by ctest?
I'd like to add the difference image when a test fails.
Thanks.
Sylvain
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Jan 16, 2008 2:11 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
> I think that is your problem. If you plugin is ONLY linking against
> bulmalib BUT aplinteligentesview is defined in bulmacont executable,
> then the linking for the plugin will NOT be possible because the
> plugin is looking for a
A Dimecres 16 Gener 2008, [EMAIL PROTECTED] va escriure:
> On Wednesday 16 January 2008 11:05:04 am Leopold Palomo-Avellaneda wrote:
> > Linking CXX shared library libpluginregistrodeiva.dylib
> > Undefined symbols:
>
> [snip]
>
> > "FichaBc::qt_metacall(QMetaObject::Call, int, void**)", referenc
A Dimecres 16 Gener 2008, Mike Jackson va escriure:
> On Jan 16, 2008, at 1:36 PM, Leopold Palomo-Avellaneda wrote:
> > A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
> >> Leopold Palomo-Avellaneda wrote:
> >>> A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
> Leopold Palomo-Avellaned
On Wednesday 16 January 2008 11:05:04 am Leopold Palomo-Avellaneda wrote:
>
> Linking CXX shared library libpluginregistrodeiva.dylib
> Undefined symbols:
[snip]
> "FichaBc::qt_metacall(QMetaObject::Call, int, void**)", referenced from:
> vtable for RegistroIvain registroiva.o
> Regi
On Jan 16, 2008, at 1:36 PM, Leopold Palomo-Avellaneda wrote:
A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
Leopold Palomo-Avellaneda wrote:
A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
Leopold Palomo-Avellaneda wrote:
Linking CXX shared library libpluginregistrodeiva.dylib
Un
A Dimecres 16 Gener 2008, Benjamin Reed va escriure:
> On Jan 16, 2008 1:05 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> wrote:
> > "non-virtual thunk to FichaBc::empresaBase()", referenced from:
> > vtable for RegistroIvain registroiva.o
> > vtable for RegistroIvaViewin moc_regi
On Jan 16, 2008 1:05 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> wrote:
> "non-virtual thunk to FichaBc::empresaBase()", referenced from:
> vtable for RegistroIvain registroiva.o
> vtable for RegistroIvaViewin moc_registroivaview.o
I've seen these types of errors before if you'
A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
> Leopold Palomo-Avellaneda wrote:
> > A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
> >> Leopold Palomo-Avellaneda wrote:
> >
> > Linking CXX shared library libpluginregistrodeiva.dylib
> > Undefined symbols:
> > "aplinteligentesview::apl
Leopold Palomo-Avellaneda wrote:
A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
Leopold Palomo-Avellaneda wrote:
Linking CXX shared library libpluginregistrodeiva.dylib
Undefined symbols:
"aplinteligentesview::aplinteligentesview(Empresa*, QWidget*)", referenced
from:
linprevco
A Dimecres 16 Gener 2008, Brandon Van Every va escriure:
> On Jan 16, 2008 12:45 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]>
wrote:
> > A Dimecres 16 Gener 2008, Brandon Van Every va escriure:
> > > I wonder if this is the "Apple linker always prefers dynamic libs"
> > > problem. Search the
A Dimecres 16 Gener 2008, Bill Hoffman va escriure:
> Leopold Palomo-Avellaneda wrote:
> > Hi,
> >
> > I'm one of the developers of a free software project [1]. I have made the
> > transition from qmake to cmake. The project has several targets (one lib
> > and 3 exes, and a lot of plugins).
> >
>
Leopold Palomo-Avellaneda wrote:
Hi,
I'm one of the developers of a free software project [1]. I have made the
transition from qmake to cmake. The project has several targets (one lib and
3 exes, and a lot of plugins).
I can compile the whole project in a GNU/Linux box with:
mkdir build
cd
On Jan 16, 2008 12:45 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> wrote:
> A Dimecres 16 Gener 2008, Brandon Van Every va escriure:
> >
> > I wonder if this is the "Apple linker always prefers dynamic libs"
> > problem. Search the mailing list archives for that.
>
> I have this:
>
> add_libr
A Dimecres 16 Gener 2008, Brandon Van Every va escriure:
> On Jan 16, 2008 12:16 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]>
wrote:
> > without any problem. Howeber, when I try to compile the project in OSX, I
> > can compile the libs, one exec but it fails with the first plugin. I have
> >
On Jan 16, 2008 12:16 PM, Leopold Palomo-Avellaneda <[EMAIL PROTECTED]> wrote:
>
> without any problem. Howeber, when I try to compile the project in OSX, I can
> compile the libs, one exec but it fails with the first plugin. I have
> isolated the problem in this:
>
> Linking CXX shared library lib
Hi,
I'm one of the developers of a free software project [1]. I have made the
transition from qmake to cmake. The project has several targets (one lib and
3 exes, and a lot of plugins).
I can compile the whole project in a GNU/Linux box with:
mkdir build
cd build
cmake ../
make
without any pr
CMAKE_CURRENT_SOURCE_DIR
On Jan 16, 2008, at 8:30 AM, Sören Freudiger wrote:
Hi
Is there a way to find out in which directory I am?
We have this kind of structure:
/proj/source/package1/a.h
/proj/source/package1/a.h
/proj/source/pack
Sean McBride wrote:
On 1/15/08 9:59 AM, Mike Jackson said:
In addition to what other's said, I'll just add the following:
Funny.. last time I asked I was told to use "i386 ppc" which did not
work and so I started adding the flags myself. Using a ";" instead of
a space does allow universal b
Hi
Is there a way to find out in which directory I am?
We have this kind of structure:
/proj/source/package1/a.h
/proj/source/package1/a.h
/proj/source/package1/CMakePackage.txt
/proj/source/package2/b.h
/proj/source/package2/b.cpp
/p
Andreas Pakulat wrote:
> Hi,
>
> does anybody know of a "built-in" way of determining the c++ compiler
> version? Specifically for GNU gcc?
>
> Or do I have to run CMAKE_CXX_COMPILER with --version and extract the
> information myself?
http://dev.openwengo.org/trac/openwengo/trac.fcgi/browser/
Hi,
does anybody know of a "built-in" way of determining the c++ compiler
version? Specifically for GNU gcc?
Or do I have to run CMAKE_CXX_COMPILER with --version and extract the
information myself?
Andreas
--
You are fairminded, just and loving.
___
Quoting Alexander Neundorf <[EMAIL PROTECTED]>:
On Tuesday 15 January 2008, Brad King wrote:
Rodolfo Schulz de Lima wrote:
> Bill Hoffman wrote:
>> Something like this:
>>
>> find_package(bar REQUIRED)
>> add_executable(foo foo.cxx)
>> target_link_libraries(foo bar)
>
> This would be GREAT! Wha
39 matches
Mail list logo
