Am 23.11.2011 22:35, schrieb Michael Hertling:
Out of curiosity - I have not worked with RPM for ages: Are these
warnings and the related overlinking due to transitive dependencies
really an issue or just an inconvenience? Personally, I distinguish
between real overlinking, i.e. pulling in librar
Hi all!
Good news - ccmake was created, but for the previous
stable version (2.6.4).
I still didn't understand what is the problem with ccmake
in the last version (2.8.6).
Best regards,
Mikhail
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/
On 2011-11-23 22:35+0100 Michael Hertling wrote:
All this to quiet rpmlint warnings
Out of curiosity - I have not worked with RPM for ages: Are these
warnings and the related overlinking due to transitive dependencies
really an issue or just an inconvenience? Personally, I distinguish
betw
On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
> cmake-2.8.6 has the following documentation of the
> LINK_INTERFACE_LIBRARIES property for targets:
>
>LINK_INTERFACE_LIBRARIES
> List public interface libraries for a shared library or executable.
>
> By default linking to a shar
Hi,
thanks for this very nice cmake. I switched just recently to get
lightspark (lightspark.github.com)
crossplatform, and it worked really smooth.
One question, though: I cannot seem to find a way to _not_
build/install the import libraries (foobar.dll.a) on win32.
I do not need them, because I'
On 2011-11-23 11:11+0100 Rolf Eike Beer wrote:
On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
In sum, from this experiment it looks like I will have to set
LINK_INTERFACE_LIBRARIES to empty for all PLplot library targets that
depend on other library targets (e.g., B, C, D, and E, above, but _no
Hello.
I've just found an issue with link_directories and cmake 2.8.5.
If I give an absolute but not normalized path like
c:/bla-bla-bla/../bla/bla as its argument (with default CMP0015),
cmake thinks it is relative path and shows a warning about explicitly undefined
policy.
Also it normalizes pa
On 11/23/2011 11:11 AM, Rolf Eike Beer wrote:
>> On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
>
>>> In sum, from this experiment it looks like I will have to set
>>> LINK_INTERFACE_LIBRARIES to empty for all PLplot library targets that
>>> depend on other library targets (e.g., B, C, D, and E, abo
Hi,
I'm working on an embedded project using a Microchip microcontroller. I want to
use Cmake to do the configuration so that I can
store the project and build settings under change control, as well as have the
configuration compatible with development windows
machines, and an automated build
On 2011-11-23 10:44+0100 Michael Wild wrote:
On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
cmake-2.8.6 has the following documentation of the
LINK_INTERFACE_LIBRARIES property for targets:
LINK_INTERFACE_LIBRARIES
List public interface libraries for a shared library or executable.
> Hi
>
> I'm trying to use cminpack. I've downloaded cminpack 1.1.3 and configure
> it with cmake to create a Xcode 3.2 project. After building the xcode
> project successfully I found that it generates a debug directory which
> contains the library or if the shared_libs option in cmake was on or o
On Wed, Nov 23, 2011 at 1:26 PM, John Drescher wrote:
> On Wed, Nov 23, 2011 at 12:30 PM, Stephen Kelly wrote:
>> David Demelier wrote:
>>
>>> Hello,
>>>
>>> I'm creating a library that use a lot of internal code (not static
>>> because it should be visible by other compilation units) so I would
On Wed, Nov 23, 2011 at 12:30 PM, Stephen Kelly wrote:
> David Demelier wrote:
>
>> Hello,
>>
>> I'm creating a library that use a lot of internal code (not static
>> because it should be visible by other compilation units) so I would like
>> to don't export any symbols but only the one I want.
>>
David Demelier wrote:
> Hello,
>
> I'm creating a library that use a lot of internal code (not static
> because it should be visible by other compilation units) so I would like
> to don't export any symbols but only the one I want.
>
> Usually you use __declspec(dllexport) for windows but on uni
Hi,
gcc supports symbol visibility also. Check http://gcc.gnu.org/wiki/Visibility
On Wed, Nov 23, 2011 at 5:52 PM, David Demelier
wrote:
> Hello,
>
> I'm creating a library that use a lot of internal code (not static because
> it should be visible by other compilation units) so I would like to
Hello,
I'm creating a library that use a lot of internal code (not static
because it should be visible by other compilation units) so I would like
to don't export any symbols but only the one I want.
Usually you use __declspec(dllexport) for windows but on unix and gcc
everything is exported
Clinton,
I did a small test and it works with qmake because phonon is the
standard search paths. It justs add -lphonon to the compiler command
line.
If not patched, there should be a note in the CMake FindQt4
documentation about the fact that it doesn't support finding phonon as
a 3rd party modul
On Wed, Nov 23, 2011 at 8:53 AM, Yegor Derevenets
wrote:
> Hi All,
>
> The following Qt program crashes with access violation when being built
> on Windows by Microsoft Visual Studio 2010 using cmake 2.8.6 and doesn't
> crash when being built using qmake:
>
> #include
> #include
>
> int main(int
Hi All,
The following Qt program crashes with access violation when being built
on Windows by Microsoft Visual Studio 2010 using cmake 2.8.6 and doesn't
crash when being built using qmake:
#include
#include
int main(int argc, char *argv[]) {
QTextStream qin(stdin, QIODevice::ReadOnly);
> On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
>> In sum, from this experiment it looks like I will have to set
>> LINK_INTERFACE_LIBRARIES to empty for all PLplot library targets that
>> depend on other library targets (e.g., B, C, D, and E, above, but _not_
>> main or A) created by our build sys
On 11/23/2011 10:25 AM, Alan W. Irwin wrote:
> cmake-2.8.6 has the following documentation of the
> LINK_INTERFACE_LIBRARIES property for targets:
>
> LINK_INTERFACE_LIBRARIES
>List public interface libraries for a shared library or executable.
>
>By default linking to a shared
cmake-2.8.6 has the following documentation of the
LINK_INTERFACE_LIBRARIES property for targets:
LINK_INTERFACE_LIBRARIES
List public interface libraries for a shared library or executable.
By default linking to a shared library target transitively links to
targets with w
22 matches
Mail list logo
