on Tue May 15 2012, Michael Jackson
wrote:
> There was a long discussion about the limitations of ninja on each
> platform on the mailing list just before the last release. That is
> where the decisions were made to limit ninja to Linux only at this
> point.
>
> That last thread was on April 17
On May 16, 2012, at 8:44 AM, Dave Abrahams wrote:
>
> on Tue May 15 2012, Michael Jackson
> wrote:
>
>> There was a long discussion about the limitations of ninja on each
>> platform on the mailing list just before the last release. That is
>> where the decisions were made to limit ninja to Li
We have a small open-source project (http://dream3d.bluequartz.net) where we
are currently releasing binaries for Windows and OS X but not for Linux due to
our lack of knowledge on how to properly release them. Our project depends on
the following projects:
Qt 4.7 (I think it will run with 4.
Taking a quick look around, here's what I'm seeing:
Current unresolved Ninja issues that are filed in the bug tracker:
http://public.kitware.com/Bug/view.php?id=13067
http://public.kitware.com/Bug/view.php?id=13073
http://public.kitware.com/Bug/view.php?id=13145
http://public.kitware.com/Bug/view
Ninja is currently not totally working on mac and windows.
The limitations are:
Windows: file level dependencies are not working.
Mac: Frameworks and application bundles are not working.
Here are the dashboards with the failing tests:
http://open.cdash.org/viewTest.php?onlyfailed&buildid=2281
Hi,
Am Mittwoch, 16. Mai 2012 schrieb Michael Jackson :
> We have a small open-source project (http://dream3d.bluequartz.net)
> where we are currently releasing binaries for Windows and OS X but not for
> Linux due to our lack of knowledge on how to properly release them. Our
> project depends o
On May 16, 2012, at 1:50 PM, Andreas Pakulat wrote:
> Hi,
>
> Am Mittwoch, 16. Mai 2012 schrieb Michael Jackson :
> We have a small open-source project (http://dream3d.bluequartz.net) where we
> are currently releasing binaries for Windows and OS X but not for Linux due
> to our lack of knowl
A commercial app might well use cmake to drive the linux packaging,
but if you want your app to become a first class citizen on Linux,
you should let the distros do the packaging. (Or better yet,
become a Debian developer and walk it through the process
yourself, but following the Debian way. Onc
Hi,
On Wed, May 16, 2012 at 8:19 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
>
> On May 16, 2012, at 1:50 PM, Andreas Pakulat wrote:
>
> > Hi,
> >
> > Am Mittwoch, 16. Mai 2012 schrieb Michael Jackson :
> > We have a small open-source project (http://dream3d.bluequartz.net)
> where
2012/5/16 Michael Jackson :
>
> On May 16, 2012, at 1:50 PM, Andreas Pakulat wrote:
> Andreas,
> Thanks for the ideas. I use bundleUtilities for OS X but not for Linux. I
> should adapt my code to also include Linux. One of the issues I have is that
> I have an HDF5 and Qwt "external" libraries
On Tue, May 15, 2012 at 1:14 PM, Eric Noulard wrote:
> 2012/5/15 Robert Dailey :
> >
> > On Tue, May 15, 2012 at 7:34 AM, Dave Abrahams
> wrote:
> >>
> >> For me, no. I'm trying to make a transition to CMake in a community
> >> where this is being seen as a problematic limitation.
> >
> >
> > I
On Tue, May 15, 2012 at 3:00 PM, Dave Abrahams wrote:
>
> on Tue May 15 2012, Robert Dailey wrote:
>
> > On Tue, May 15, 2012 at 7:34 AM, Dave Abrahams
> wrote:
> >
> >
> > on Mon May 14 2012, Robert Dailey <
> rcdailey.lists-Re5JQEeQqe8AvxtiuMwx3w-AT-public.gmane.org> wrote:
> >
> > >
2012/5/16 Dan Kegel :
> A commercial app might well use cmake to drive the linux packaging,
> but if you want your app to become a first class citizen on Linux,
> you should let the distros do the packaging. (Or better yet,
> become a Debian developer and walk it through the process
> yourself, bu
On May 16, 2012, at 3:41 PM, Eric Noulard wrote:
> 2012/5/16 Michael Jackson :
>>
>> On May 16, 2012, at 1:50 PM, Andreas Pakulat wrote:
>> Andreas,
>> Thanks for the ideas. I use bundleUtilities for OS X but not for Linux. I
>> should adapt my code to also include Linux. One of the issues I
Michael Jackson wrote:
> That was VERY informative. This is what I was afraid of. With Windows and OS
> X even though there are 3 or 4 versions if you build for the earliest one (XP
> or 10.5) the binary has a really good chance of still running on the latest
> (Win7 or Lion). With Linux and so
On Wed, May 16, 2012 at 1:09 PM, Dan Kegel wrote:
> The source route *is* the best way possible, from the Linux point of view!
And yes, you should try hard to be compatible with the distros' versions
of all libraries (like Qwt). (Using a private copy of libraries is generally
frowned upon, as t
2012/5/16 Robert Dailey :
> On Tue, May 15, 2012 at 1:14 PM, Eric Noulard
>> > I'm assuming this is being setup so users can download pieces of boost
>> > individually and only use the parts they want. I'm glad that Boost is
>> > making
>> > a real effort to use CMake. I think such an influential
On 05/10/2012 03:25 AM, Petr Kmoch wrote:
> we're using cmake to generate Intel Fortran .vfproj files and some of
> my developers were asking why include directories in the project
> always include X and X/ for every directory X specified
> via include_directories(). Looking at cmake source code, t
2012/5/16 Michael Jackson :
[...]
>
> That was VERY informative. This is what I was afraid of. With Windows and OS
> X even though there are 3 or 4 versions if you build for the earliest one (XP
> or 10.5) the binary has a really good chance of still running on the latest
> (Win7 or Lion).
Yes
On Wed, May 16, 2012 at 1:32 PM, Eric Noulard wrote:
> You may have a look at OBS: https://build.opensuse.org/
> it may help you with "many-distro" building.
Probably worth trying just as a way to test compatibility,
even if you don't then ship the resulting packages.
I like the idea behind OBS,
On Wed, May 16, 2012 at 3:20 PM, Eric Noulard wrote:
> Sure and I'm pretty sure CMake community and developers in the first place
> try hard to make CMake as robust and as consistent as they can,
> i.e. making it a serious tool in many sense.
>
> Please don't be mad at me, as you probably altready
I have a library, libA, that depends on another library, libB, with
this structure:
My Program -> libA -> libB
In my program, if I only link to libA, I get linker errors that it
can't find things in libB, and these errors are fixed if I also link
My Program to libB. This makes sense, but is there
Great,
I believe the External Project is what I need..
Thanks!
totte
On 5/15/2012 2:43 PM, Leif Walsh wrote:
Look at things involving the IMPORTED property of add_library. You probably
want to check the headers in to your repo. Or use or create a FindLibXml2.cmake.
Or if you are compiling lib
Hi,
I am building a C++ library, using Cmake. When creating the build files from
CMkae UI, I have a BUILD_SHARED_LIBS option, allowing the user to create a
static, or a dll version of the library.
In addition to the 'main' library, and in the same Cmkae project, I have a C
wrapper, that shoul
On Mon, Apr 02, 2012 at 02:21:10PM +0200, Nicolas Desprès wrote:
> Hi,
>
> It looks like an issue in the generator. The symlink is created as a
> side effect of a rule and not mentioned in the output files. That's
> why it does not get removed. I have pushed a patch on my CMake's
> github clone th
> That was VERY informative. This is what I was afraid of. With Windows and OS
X even though there are 3 or 4 versions if you build for the earliest one (XP
or 10.5) the binary has a really good chance of still running on the latest
(Win7 or Lion). With Linux and so many distributions I don't h
Ralph Barth will be out of the office starting 17/05/2012 and will be
returning on 21/05/2012.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
WLLM related questions pls. contact Sebastian Neusüß and Jens Keil.
Theo Price Feed from EDRE pls contact Jens Keil
On Wed, May 16, 2012 at 4:20 PM, Craig Scott
wrote:
> Don't give up just yet! There are other options which might meet your
> needs. No-one appears yet to have mentioned the LSB (Linux Standards Base)
> and it is designed to solve problems just like yours. Admittedly, it will
> take a little bit o
On 5/16/2012 3:49 PM, Robert Dailey wrote:
> involved with CMake will help push Kitware to realize how serious
people are
> taking their products and maybe they'll make a move to "professionalize"
> them.
So, I do take offense to this language.
Kitware does take CMake seriously and we are al
Using the keyword SHARED in the add_library command will always build a shared
library regardless of the BUILD_SHARED_LIBS value.
On May 16, 2012, at 6:15 PM, Totte Karlsson wrote:
> Hi,
> I am building a C++ library, using Cmake. When creating the build files from
> CMkae UI, I have a BUILD
Thanks very much for the feedback. I will look into the module stuff,
where the compiler puts it etc.
Petr
On Wed, May 16, 2012 at 10:24 PM, Brad King wrote:
> On 05/10/2012 03:25 AM, Petr Kmoch wrote:
>> we're using cmake to generate Intel Fortran .vfproj files and some of
>> my developers were
Hi David,
there's a target property LINK_INTERFACE_LIBRARIES (and
per-configuration variants) which can be used for this purpose.
Starting with 2.8.7, target_link_libraries() also accepts
LINK_INTERFACE_LIBRARIES as a new argument mode, setting the property
instead of linking.
Petr
On Wed, May 1
32 matches
Mail list logo
