Hi,
I am trying to build a library with cmake using QT4 tools (moc, wrap) using
a master cmake script and lib/project related subscript. The thing is that I
have a build error then the one of the library (the one that uses QT4) tries
to link. Here's the log:
Linking CXX static library
/Users/fcmo
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> Am Freitag 14 September 2007 schrieb Goswin von Brederlow:
>> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
>> > On a Unix-like OS, you can execute "uname -m" to get the machine
>> > architecture (but this is probably not really portable to M$...):
>>
Dizzy <[EMAIL PROTECTED]> writes:
> On Friday 14 September 2007 20:08:13 Goswin von Brederlow wrote:
>> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
>> > On a Unix-like OS, you can execute "uname -m" to get the machine
>> > architecture (but this is probably not really portable to M$...):
>>
>>
Gregory C. Sharp wrote:
Hi,
Does Cmake have a macro that tests how a compiler
defines inline, such as autoconf's AC_C_INLINE?
Thanks,
Greg
Hi Greg,
I couldn't find one, so I ported AC_C_INLINE to CMake. Since there's no
equivalent of autoheader to make the config.h.in, I just used
ADD_DEFI
Am Freitag 14 September 2007 schrieb Goswin von Brederlow:
> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
> > On a Unix-like OS, you can execute "uname -m" to get the machine
> > architecture (but this is probably not really portable to M$...):
>
> Not even portable across systems of the same arc
Hi,
Does Cmake have a macro that tests how a compiler
defines inline, such as autoconf's AC_C_INLINE?
Thanks,
Greg
--
Gregory C. Sharp
Dept. of Radiation Oncology
Massachusetts General Hospital
[EMAIL PROTECTED] / 617-724-3866
http://gray.mgh.harvard.edu
The information transmitted in this e
On Friday 14 September 2007 20:09:14 Goswin von Brederlow wrote:
> "Mathieu Malaterre" <[EMAIL PROTECTED]> writes:
> > How about:
> >
> > CMAKE_SYSTEM_PROCESSOR
>
> What does that say on i686? i486 or i686? What I want is the
> architecture, not the specific cpu we currently run on.
It does not s
On Friday 14 September 2007 20:08:13 Goswin von Brederlow wrote:
> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
> > On a Unix-like OS, you can execute "uname -m" to get the machine
> > architecture (but this is probably not really portable to M$...):
>
> Not even portable across systems of the sa
"Mathieu Malaterre" <[EMAIL PROTECTED]> writes:
> How about:
>
> CMAKE_SYSTEM_PROCESSOR
What does that say on i686? i486 or i686? What I want is the
architecture, not the specific cpu we currently run on.
MfG
Goswin
___
CMake mailing list
CMak
"wim van hoydonck" <[EMAIL PROTECTED]> writes:
> On a Unix-like OS, you can execute "uname -m" to get the machine
> architecture (but this is probably not really portable to M$...):
Not even portable across systems of the same architecture nor
accurate. On IA32 (x86) you want to compile for i486
Jack Kelly <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow wrote:
>> Jack Kelly <[EMAIL PROTECTED]> writes:
>> What happens when CFLAGS is already set in the environment or when I
>> need to just extend it. I guess what I'm looking for is the Makefile
>> syntax
>>
>> CFLAGS += something
> # Try
Hi All,
I am new to cmake, thank you for the awesome product. I am using the free
VC++ 5.0 Express with the Platform SDK, I am curious why cmake doesn't
report this as the free VC compiler? I am using cmake version 2.4-patch 7.
C:\DOCUME~1\GEORGE~1\Desktop\build>cmake -G"NMake Makefiles" ..\src
On Friday 14 September 2007 16:19:05 Bill Hoffman wrote:
> Dizzy wrote:
> > What you are sugesting solves the problem for installable libraries
> > (which were installed in a previous to "cmake time", the time where
> > FIND_LIBRARY() runs). Problem with "convenience libraries" of a project
> > is
Dizzy wrote:
On Thursday 13 September 2007 15:08:30 you wrote:
Thinking out of the box, here is one way I solved this problem. Say
your first project builds a library Foo. Then install that library in
what ever location you want to install it. Then set an environment
variable "FOO_ROOT" that
On 9/14/07, wim van hoydonck <[EMAIL PROTECTED]> wrote:
> On 9/14/07, Jack Kelly wrote:
> > Goswin von Brederlow wrote:
> > > Jack Kelly writes:
> > >> # One way would be to have a file i486.cmake:
> > >> SET(ARCH i486)
> > >> # and whatever else...
> > >
> > > And cmake automatically includes the
On 9/14/07, Jack Kelly wrote:
> Goswin von Brederlow wrote:
> > Jack Kelly writes:
> >> # One way would be to have a file i486.cmake:
> >> SET(ARCH i486)
> >> # and whatever else...
> >
> > And cmake automatically includes the right file then?
> >
> >> # A file called x86_64.cmake:
> >> SET(ARCH x8
*smak self*
I swear I thought I tried that permutaion before, but .. It seems to be
correct now (Ive got a few other microsoft transition errors to deal
with but that one is gone now!)
Many thanks!
Question: why didn't the Cmake find the fltk directories and libraries?
I wound up adding the l
I have not yet contributed to the wiki or anything to CMake yet so I
might not be in position to give advice, but if I look at the main
page for CMake on the wiki I can see a page named Platform Dependent
Issues. I don't think the faq is a good place for platform specific
stuff or stuff which work
Goswin von Brederlow wrote:
Jack Kelly <[EMAIL PROTECTED]> writes:
What happens when CFLAGS is already set in the environment or when I
need to just extend it. I guess what I'm looking for is the Makefile
syntax
CFLAGS += something
# Try this:
SET(CMAKE_C_FLAGS "$ENV{CFLAGS} -fno-builtin ...")
"Sanchez, Juan" <[EMAIL PROTECTED]> writes:
> Hi,
> I was aware that fPIC induces a performance penalty, but I didn't realize it
> was bad as you mention (30% degradation). My preference is not reusing the
Some people claim 30% penaltiy. This number is obviously highly
dependant on the code and
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/13/07, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>>
>> For dynamic code (in C/C++/obj-c/fortran/anythign with C linkage) you
>> must use -fPIC or variant thereof because otherwise your jump labels
>> will be too small and linking will fa
Oops please refer to the file attached to the previous mail, not to
the inline text, I've messed it up with a wrong >/< => +/-
translation. Sorry about that.
On 9/14/07, Nicolas Burrus <[EMAIL PROTECTED]> wrote:
> All right, was I propose is the following patch (which seems to work
> fine and not
All right, was I propose is the following patch (which seems to work
fine and not pertubate CPack). Then to set the component to install at
configure time, one just need to add:
SET(CMAKE_INSTALL_COMPONENT "Runtime")
Any objection against this patch? Is it possible to apply it?
Thanks,
Index: So
On Thursday 13 September 2007 15:08:30 you wrote:
> Thinking out of the box, here is one way I solved this problem. Say
> your first project builds a library Foo. Then install that library in
> what ever location you want to install it. Then set an environment
> variable "FOO_ROOT" that points to t
24 matches
Mail list logo
