On Thu, 31 Oct 2013 22:08:27 +0100
Ivan Sergio Borgonovo wrote:
[snip]
> The only difference I can spot is that others contains global symbols
> that are referenced in C files[1] or in the linker options[2] while
> the only one that doesn't get compiled and linked contains symbols
> that are ref
Microsoft believed in hidden by default for shared libraries.
Don't say things like this: people will never hide anything ever
again... ;-)
But seriously, making only those things public that are explicitly
exported has some major benefits: for one, it minimizes the probability
of clashes w
On Thu, 31 Oct 2013 21:17:11 +0100
Alexander Neundorf wrote:
> On Thursday 31 October 2013, Ivan Sergio Borgonovo wrote:
> > On Thu, 31 Oct 2013 18:01:29 +0100
> >
> > Alexander Neundorf wrote:
> > > Did you try setting the source file property "LANGUAGE" to "ASM"
> > > for these files ?
> > >
On 31 October 2013 20:21, Hendrik Sattler wrote:
>
> Giordano Khouri schrieb:
>>I am a firm believer that static libraries should have hidden
>>visibility. This is based on my experience on the Mac and may be
>>different in Linux.
>
> This is about Windows, not Linux or Mac. Linking libraries wor
On Thu, Oct 31, 2013 at 1:21 PM, Hendrik Sattler
wrote:
>
>
> Giordano Khouri schrieb:
>>I am a firm believer that static libraries should have hidden
>>visibility. This is based on my experience on the Mac and may be
>>different in Linux.
>
> This is about Windows, not Linux or Mac. Linking libr
Giordano Khouri schrieb:
>I am a firm believer that static libraries should have hidden
>visibility. This is based on my experience on the Mac and may be
>different in Linux.
This is about Windows, not Linux or Mac. Linking libraries works a bit
different there.
>A shared library (dylib, fram
On Thursday 31 October 2013, Ivan Sergio Borgonovo wrote:
> On Thu, 31 Oct 2013 18:01:29 +0100
>
> Alexander Neundorf wrote:
> > Did you try setting the source file property "LANGUAGE" to "ASM" for
> > these files ?
> > http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_sf:LANGUAGE
>
> Than
On Thu, 31 Oct 2013 18:01:29 +0100
Alexander Neundorf wrote:
> Did you try setting the source file property "LANGUAGE" to "ASM" for
> these files ?
> http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_sf:LANGUAGE
Thanks, that made the trick but I ran into another problem:
One of those asm
I am a firm believer that static libraries should have hidden visibility. This
is based on my experience on the Mac and may be different in Linux.
A shared library (dylib, framework) can export a symbol that came in from a
static library as a private extern. If the symbol is extern
(visibility=
On 2013-10-31 14:46, Hendrik Sattler wrote:
Matthew Woehlke schrieb:
On 2013-10-31 05:26, Cyrille Faucheux wrote:
On the library I'm currently working on, with Visual Studio, I have
to declare some compile definition in order to get the proper
"__declspec(dllimport)" or "__declspec(dllexport)"
something like (but probably mostly in a common header)
if( IS_THIS_PROJECT )
if( UNIX or STATIC )
set( EXPORT ) # nothing, everything is exported by default; gcc/unix
else( UNIX or STATIC )
set( EXPORT __declspec(dllexport) )
endif( UNIX or STATIC )
else( IS_THIS_PROJECT )
Matthew Woehlke schrieb:
>On 2013-10-31 05:26, Cyrille Faucheux wrote:
>> Can you tell me a bit more about "implicit compile flags [...] for
>imported
>> tagets"?
>
>See documentation on target_compile_definitions.
>
>> On the library I'm currently working on, with Visual Studio, I have
>to
>> d
On 10/31/2013 1:17 PM, Stephen Kelly wrote:
>There is a -j flag for ctest, which at enables parallel testing. Not sure
>whether it enables also parallel building.
I don't know, but I hope not. That wouldn't be a good idea because it would
try to do N*N things at once instead of N things at once,
Alexander Neundorf wrote:
> On Thursday 31 October 2013, Olaf Ryder wrote:
>> Greetings,
>>
>> I'm looking for ways to speed up CTest runs (the Experimental target). It
>> would appear the majority of the time is spent during the build step.
>>
>> 1) What exactly is happening during the Experime
Cyrille Faucheux wrote:
> Ok, great.
>
> Can you tell me a bit more about "implicit compile flags [...] for
> imported tagets"?
>
> On the library I'm currently working on, with Visual Studio, I have to
> declare some compile definition in order to get the proper
> "__declspec(dllimport)" or "__
On Thursday 31 October 2013, Ivan Sergio Borgonovo wrote:
> Hi,
>
> I'm cross compiling (avr32) with a gcc compiler under Linux and I'm
> using a framework where asm extensions aren't directly recognized by
> cmake (.x).
>
> gcc is recognized as a valid C and ASM compiler during cmake
> configura
On Thursday 31 October 2013, Olaf Ryder wrote:
> Greetings,
>
> I'm looking for ways to speed up CTest runs (the Experimental target). It
> would appear the majority of the time is spent during the build step.
>
> 1) What exactly is happening during the Experimental build step?
> 2) How does CTes
On 2013-10-31 05:26, Cyrille Faucheux wrote:
Can you tell me a bit more about "implicit compile flags [...] for imported
tagets"?
See documentation on target_compile_definitions.
On the library I'm currently working on, with Visual Studio, I have to
declare some compile definition in order to
-Original Message-
From: Dominic Walsh
To: David Cole ; cmake
Sent: Wed, Oct 30, 2013 6:06 am
Subject: RE: [CMake] Windows Visual Studio Install Configurations
unexpected behaviour
In Visual Studio | INSTALL project | Right mouse button "Build"
This does look like it must be a bug
Sorry for this -- I just noticed the other question you did send right
afterwards
Welcome!
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For mor
Iam new to the list and want to Introduce myself.
Welcome to the CMake mailing lists -- did you have a question about
CMake?
Please read the text on this page [
http://www.cmake.org/mailman/listinfo/cmake ] about what sorts of
emails make sense to send to the list.
Thanks,
David
--
Pow
Ok, great.
Can you tell me a bit more about "implicit compile flags [...] for imported
tagets"?
On the library I'm currently working on, with Visual Studio, I have to
declare some compile definition in order to get the proper
"__declspec(dllimport)" or "__declspec(dllexport)" defined (or not defi
> From: mathieu.malate...@gmail.com
> Date: Thu, 31 Oct 2013 08:54:42 +0100
> Subject: Giving my modules for adoption
> To: cmake-develop...@cmake.org
> CC: xantare...@hotmail.com
>
> Hi all,
>
> I'd like to repeat what I stated before [*]. I no longer have the
> time to maintain my cmake mod
Hi,
This sounds logical
thx for the fast reply.
Drav
Am 31.10.2013 08:59, schrieb Jakub Zakrzewski:
Hi,
QtCreator undestands CMake output. I doesn't parse CMake on its own. Basically, when you
hit "Build", the native build mechanism is invoked (on Linux it defaults to
make), which, in turn
Hi,
QtCreator undestands CMake output. I doesn't parse CMake on its own. Basically,
when you hit "Build", the native build mechanism is invoked (on Linux it
defaults to make), which, in turn, invokes CMake. If there are errors in
CMakeLists.txt, they will be shown in your build output as normal
Hello
If have just a little Question:
I noticed thadt the manuals and Helpfiles and allways describing the Way
to generate makefiles,
XCode Workspaces and Visual C/C++ Solutionfiles and right now iam using
the generated Workspaces
or Makefiles to use the native Makeutility or the VC++ or XCode
26 matches
Mail list logo
