On 8/18/07, Jack Kelly <[EMAIL PROTECTED]> wrote:
>
> I'm specifically thinking about OCaml here, but the problem generalises
> to other languages where the compiler doesn't output exactly one file.
>
> I guess the rule for CMAKE_OCaml_COMPILE_OBJECT would be
> " -c -o "
> but there doesn't seem
Further investigation reveals that it is specifically related to Python and
QT. If these options are switched off then everything is OK in the case of
building VTK.
On 8/17/07, Andrew Maclean <[EMAIL PROTECTED]> wrote:
>
> Has anyone tried building VTK or Paraview with the latest CMake CVS
> ver
Hi all,
I'm specifically thinking about OCaml here, but the problem generalises
to other languages where the compiler doesn't output exactly one file.
If I compile a .ml file using the native code compiler:
$ ocamlopt -c -o foo.cmx foo.ml
It will also produce a .o file and possibly a .cmi fi
Clemens Arth wrote:
Hi everybody,
for convenience I've located my Cmake projects on a vfat partition of
my hard disk, so I can access it from Linux and Windows without
problems. When I'm running on Linux, and I'm trying to call cmake on
the vfat partition, so that the binaries should also be
On 8/14/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
> On 8/14/07, Tristan Carel <[EMAIL PROTECTED]> wrote:
> > I will make more serious test with `advanced' options:
> > DEBIAN_PACKAGE_DEPENDS, stuff like that...
>
> If anyone has any experience with this, he should speak now or hold
> his pea
I've tried to use umask=000, which means that I had read/write/execute
permissions, without success... I'll check the dmask/fmask and exec stuff you
mentioned as soon as I'm back in my office...
Clemens
Original-Nachricht
Datum: Sat, 18 Aug 2007 11:05:57 +0200
Von: Hendrik Sat
Am Samstag 18 August 2007 09:54 schrieb Clemens Arth:
> Any ideas? I'm running UBUNTU 7.04 and the actual cmake 2.4.6; I've
> mounted the partition with
>
> /media/data vfatdefaults,utf8,umask=007,gid=46 0 1
You may want to use the dmask and fmask options instead of umask, s
Clemens Arth wrote:
/media/data vfatdefaults,utf8,umask=007,gid=46 0 1
I'm not 100% on how umask works, but I think that:
Using the user account that you tried to run CMake with, attempt to
create a file in the vfat mount, just to confirm it's a permission issue.
-- J
Hi everybody,
for convenience I've located my Cmake projects on a vfat partition of my
hard disk, so I can access it from Linux and Windows without problems.
When I'm running on Linux, and I'm trying to call cmake on the vfat
partition, so that the binaries should also be created on that
part
