I hope Gabriel gave you the right answer - he seems to know more about findlib than I do.
Will you be posting the GameTime tool at http://uclid.eecs.berkeley.edu/gametime/ ?
On 10/12/2013 11:04 AM, Gabriel Kerneis wrote:
> On Fri, Oct 11, 2013 at 07:49:27PM -0700, Jonathan Kotker wrote:
>> Try setting OCAMLFIND_CONF to the absolute path of a minimal findlib.conf file.
> This file should contain the following two lines:
> path = "/absolute/path/to/mylibdir"
> destdir = "/absolute/path/to/mylibdir"
> It is then not necessary anymore to set OCAMLPATH. Alternatively, if you prefer
> to set OCAMLPATH dynamically, you can probably use:
> path = ""
> destdir = ""
On 10/12/2013 5:49 AM, Jonathan Kotker wrote:
Thanks for that suggestion, Alex. I will try that out.
In the meantime, it seems as though a beta-tester is having a problem with the Cilly
compilation that I distributed. Here is the command that is being run:
0-py2.7.egg/gametime/cil/bin/cilly --dooneRet --domakeCFG --dosimpleMem --disall
owDuplication --noPrintLn --dopartial --partial_root_function=modexp_simple C:\g
me-1.0\demo\modexp_unrolled\modexp_simple-gt' -c -o 'C:\gametime\gametime-1.0\de
This is produced by calling the Cilly script with the same arguments, and after setting
the OCAMLPATH and CIL_FEATURES environment variables appropriately -- the latter is
defined to be 'cil.default-features'. However, the beta-tester obtains the following error
(he does not have findlib installed on his system):
Fatal error: exception Failure("Config file not found - neither /usr/etc/findlib
.conf nor the directory /usr/etc/findlib.conf.d")
Any idea what might be causing this? This also happens if the environment variables are
Thanks for any help and suggestions, and for all that has been provided so far.
On 11 October 2013 04:18, Alex Susu <firstname.lastname@example.org <mailto:email@example.com>> wrote:
I am new to findlib and ocamlfind. I didn't manage to get my module linked into the
CIL executables with the new build system, so I started looking at the Makefile, more
specifically variables OCAMLFIND_DESTDIR and then CIL_DEFAULT_PLUGINS, which is used to
write in the main folder of CIL the META file.
Turns out that an easy way to specify (is this findlib standard?) to link a module
(as a default-features module) is to create in the folder of that module (e.g.,
src/ext/zrapp) an empty file named "default".
Hope this helps :)
If there's anything more to add please don't hesitate.
On 10/10/2013 8:03 PM, Jonathan Kotker wrote:
> I used to use --load, but then one of my beta-testers informed me that he seemed to
> needed findlib, which spawned off my question to you.
> On 10 October 2013 09:53, Gabriel Kerneis <firstname.lastname@example.org
<mailto:email@example.com>> <mailto:firstname.lastname@example.org <mailto:email@example.com>>> wrote:> CILfirstname.lastname@example.org <mailto:CILemail@example.com>
> On Thu, Oct 10, 2013 at 09:29:56AM -0700, Jonathan Kotker wrote:
> > Since I am using Python to execute the Cilly driver, I managed to find a
> > way to dynamically set the environment variable OCAMLPATH (albeit
> > temporarily) from within my Python script, and it works beautifully once
> > the OCaml code has been compiled.
> Glad it works for you. I realized later that you do not even need to
> use findlib at all: you can also use --load path/to/plugin.cmxs
> explicitly. The only downside is that you need to take care of loading
> dependencies in the correct order in that case (whereas findlib will
> figure it out, using META files).
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register>
> CIL-users mailing listCILfirstname.lastname@example.org <mailto:CILemail@example.com>
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
CIL-users mailing list