congratulations! :)
please let me know when you have completed your scripts, so that i can replace
mine with your in the yars refactoring tree.
cheers,
keyan
On 26 Jan 2010, at 22:53, Judicaël Bedouet wrote:
> Thanks for your help. It is solved. A dependency between custom targets was
> miss
Thanks for your help. It is solved. A dependency between custom targets was
missing. In fact, the dependency was just between the custom command outputs
and I didn't think that setting a dependency between custom targets would
have solved the problem.
I also have had to generate objects in separat
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
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
hi,
i didnt have much time lately to look deeply into the scripts. at first i
thought that one has to add some add_dependencies, which was my first strategy,
before i wrote useocaml.cmake. but then i saw, that i removed them, because i
got the DEPENDS right. so my guess was wrong.
what you wri
Hello,
I try to compare Makefiles generated by your scripts and mine. I don't see
any big differences, except the copy rules.
While trying your scripts, I also reproduced a similar bug.
Generating file_node.cmx
Generating message_node.cmi
Generating file_node.cmi
File "/Users/judi/src/ocaml/cmak
hi,
i started to work on your scripts. very nice work!
unfortunately, i couldnt find the problem, and i cant reproduce it with my
scripts. there must be a difference somewhere.
cheers,
keyan
On 19 Jan 2010, at 00:30, Judicaël Bedouet wrote:
> Hi,
>
> Effectively, I have reproduced your two
hi,
i had the same problems before i wrote my useocaml.cmake. actually, that was
the main reasons for writing it. i solved the problems by getting all the
depencies right. my guess is, that a few additional add_depencies will solve
the problem. as soon as i have a little bit time, i will check
Hi,
Effectively, I have reproduced your two bugs by using make -j. It's not
systematic (once in ten).
>> Error: The file /Users/zahedi/Downloads/code-analysis-build/io.cmo is not
a bytecode object file
When this error occurs, it also appears that the object is being built. And
if I rerun make, li
thanks for the explanation. i hope you didnt feel offended. the uselatex.cmake
is great. without that, i wouldn't even had a clue where to start :)
cheers,
keyan
On 18 Jan 2010, at 17:12, Moreland, Kenneth wrote:
> The reason the UseLATEX.cmake script copies files to the binary directory is
>
The reason the UseLATEX.cmake script copies files to the binary directory is
because the latex compiler has no equivalent to the -I flag. It always looks
for files with respect to the directory in which the command was run. Thus,
the easiest way to do an out-of-source build is to simply copy t
hi,
> Indeed, it is much more sophisticated, so it may be more bugged ;-)
i can help debugging :)
> >> shell i send you my scripts to take a look?
> It's not necessary. I have downloaded the refactoring branch of yars. Thanks.
oh, ok, then you should have the newest version (last yars revision
Indeed, it is much more sophisticated, so it may be more bugged ;-)
>> shell i send you my scripts to take a look?
It's not necessary. I have downloaded the refactoring branch of yars.
Thanks.
I comment my OCaml scripts and I send you, so that you could also have a
look.
I have took a look at yo
On Thu, Jan 14, 2010 at 5:11 AM, Keyan wrote:
> hi,
>
> ups ... i thought i replied to the list. thanks for the link. i will adapt my
> find-script to the requirements and maintain the package.
You should work with Judicaël to combine the best of both of your
works together into one FindOCaml an
d be interesting to
integrate it in CMake. Do you need some explanations to see if it's possible
to integrate OCaml in CMake ?
Best regards,
J. Bedouet
-- Forwarded message --
From: Keyan
To: Philip Lowman
Date: Thu, 14 Jan 2010 11:11:56 +0100
Subject: Re: [CMake] ANN: UseOcam
hi,
ups ... i thought i replied to the list. thanks for the link. i will adapt my
find-script to the requirements and maintain the package.
cheers,
keyan
On 14 Jan 2010, at 03:46, Philip Lowman wrote:
> On Mon, Jan 11, 2010 at 3:39 AM, Keyan wrote:
>>> It looks like a couple of the macros do
On Mon, Jan 11, 2010 at 3:39 AM, Keyan wrote:
>> It looks like a couple of the macros don't have the OCAML_ name prefix
>> added to them. For example, COPY_FILE & GET_DEPENDENCIES. You should
>> add the prefix to them as well to prevent name collision when other
>> people use your code.
>
>thank
On Sat, Jan 9, 2010 at 2:11 PM, Keyan wrote:
> Hi,
>
> adapted from UseLATEX.cmake, i wrote a UseOcaml.cmake script, which can be
> found here:
>
> http://yars.svn.sourceforge.net/viewvc/yars/branches/yars-refactoring/modules/UseOcaml.cmake?revision=509&view=markup
>
> it is not complete yet, but
Hi,
adapted from UseLATEX.cmake, i wrote a UseOcaml.cmake script, which can be
found here:
http://yars.svn.sourceforge.net/viewvc/yars/branches/yars-refactoring/modules/UseOcaml.cmake?revision=509&view=markup
it is not complete yet, but it allows to easily compile ocaml-binaries in the
followi
19 matches
Mail list logo
