On 2010-01-24 17:52-0600 Poor Yorick wrote:
while building plplot-5.95 with cmake-2.8.0, I got this error:
I will contact you separately off the CMake list since this seems
to be a PLplot build-system issue rather than a CMake one.
Alan
__
Alan W. Irwin
Astronomical
On 2010-01-26 00:28+0100 Judicaël Bedouet wrote:
I see one solution : add a macro to create an only target with all OCaml
libraries and executables, but it's not perfect.
This issue should be straighforward to solve with proper dependencies for
_both_ custom targets and custom command OUTPUT f
Good question.
sadly http://www.cmake.org/Bug/roadmap_page.php does not include cmake.
Brian
On Fri, Jan 22, 2010 at 9:17 AM, Tim St. Clair wrote:
> When is the planned release of 2.8.1?
> Is there a online roadmap?
>
> --
> Cheers,
> Timothy St. Clair
>
__
Hi,
I think I have found the problem. It's in the structure of the Makefile
generated by CMake. For each target, make is called on a sub Makefile and
this is problematic for OCaml. I have reproduced the problem with an
handwritten Makefile (see attachment).
Try make -j all2 and make -j all1. The
Alan W. Irwin wrote:
> messages for these files they deal with the following compilers/platforms.
>
> * gfortran on Cygwin
>
> * gfortran under MinGW
I think these work out of the box in 2.8.0. However, there has been more
development since that release (see bottom of message). They almost
cer
I have overcome the issues with MSVCR90D.dll and MSVCP90d.dll by installing
Visual Studio 9 SP1. Which seems to fix references to amd64 dlls. Why this
is not in the web update is anyone's guess. Just more MS super spectacular
awesomeness.
Now on to my latest (CMAKE) problem. I can build and ru
The current project that I am working on has multiple projects layered through
subdirectories. The project was a conversion from traditional makefiles and
when we do a cmake build from the root of the source tree all is done
correctly. The issue comes to when we try and build a single component
Hi,
please apply the attached patch to Modules/CMakeCompilerABI.h (current CVS,
but 2.8.0 should work too).
You should then get the variables CMAKE_(C|CXX)_COMPILER_ABI set to
either "ELF ARM" or "ELF ARMEABI".
Please let me know if this works for you and also whether you think these
names are
On Monday 25 January 2010, Jens Auer wrote:
> Hi,
>
> I am trying to port a project from VC++ to a cmake build-system.
> Unfortunately, the project has a little problem: There are several
> libraries and some of them generate files using uic (Qt3). Cmake can
> handle this pretty well, but in one ca
John Drescher wrote:
I am testing running cmake to generate Visual Studio 2005 projects
under wine and things are going good. I have built 2 projects without
any problems then the third project had the following error:
CMake Error at C:/Program Files/CMake
2.8/share/cmake-2.8/Modules/CMakeFortra
On Mon, Jan 25, 2010 at 7:37 AM, Marcel Loose wrote:
> Hi all,
>
> IMHO the macro Subversion_WC_INFO in FindSubversion.cmake should not do
> a SEND_ERROR, when the 'svn info' command fails. This makes the macro
> useless if you want to be able to use it both on SVN working copies and
> SVN export
On Mon, Jan 25, 2010 at 2:49 AM, Eric Noulard wrote:
> 2010/1/25 Nicholas Yue :
> > Hi,
> >
> > I am attempting to use CPack to package up a SWIG module I am
> > distributing.
> >
> > I have no problem with CPack on Linux but on Windows, I have some
> > difficulty.
> >
> > CMAKE CONFIG
> >
John Drescher wrote:
Can you please help as how I could specify the number of threads to be used
in the command line builds i.e. something like
(For nmake)
Cmd > nmake –j5
(For Visual Studio 2008)
cmd> cmake –-build . –j5
Use vcbuild or msbuild
You can use jom, or gmake.
Jom is an nmak
Hi,
I am trying to port a project from VC++ to a cmake build-system.
Unfortunately, the project has a little problem: There are several
libraries and some of them generate files using uic (Qt3). Cmake can
handle this pretty well, but in one case, there are two libraries which
include generated hea
Hi,
Is there a way to specify the output directory of QT_WRAP_UI where the
generated header files will be put? I am porting a VC++-based project
and files are included with the relative paths, so if the ui file is
placed in
Lib1/dir1/file1.ui
I want the output generated in
CMAKE_BINARY_DIR/lib1/di
Hi all,
IMHO the macro Subversion_WC_INFO in FindSubversion.cmake should not do
a SEND_ERROR, when the 'svn info' command fails. This makes the macro
useless if you want to be able to use it both on SVN working copies and
SVN exported trees. Either make this behaviour configurable, or change
it to
Hi
I think i have solved something now, it was just too easy for my sceptical
mind.
Anyway, I found out that NSIS installer on windows xp (which is the only
platform this currently needs to work on) already generates a registry
entry, and i only need to read it
in the Find*.cmake file, which app
Alexander Neundorf wrote:
> On Friday 22 January 2010, Yegor Yefremov wrote:
>> Hello,
>>
>> I have two toolchains to compile programs for ARM Debian: one supporting
>> older ABI (Etch) and one for EABI (Lenny). How can I determine the ABI
>> version using CMake?
>
> Please post the output of the
18 matches
Mail list logo
