From: Jonathan K. <adv...@gm...> - 2011-02-28 08:08:31
|
Hello World. I am planning to use CIL as part of the research tool that I am writing. Currently, my code constructs and runs a system call that runs the cilly driver on my local machine, along with specific arguments. My question is this: if I were to release the tool as an open-source tool for all to see and use, would it be possible to only include the Cilly driver (or a small subset of the CIL files) as part of the files for the tool, or would a user have to install CIL (and thus perl and ocaml) before being able to run and use my tool? Thanks, Jon. |
From: 林楠 <xia...@gm...> - 2011-02-28 08:36:40
|
run make and you will get an executable of your platform On Feb 28, 2011 4:08 PM, "Jonathan Kotker" <adv...@gm...> wrote: > Hello World. > > I am planning to use CIL as part of the research tool that I am writing. > Currently, my code constructs and runs a system call that runs the cilly > driver on my local machine, along with specific arguments. My question is > this: if I were to release the tool as an open-source tool for all to see > and use, would it be possible to only include the Cilly driver (or a small > subset of the CIL files) as part of the files for the tool, or would a user > have to install CIL (and thus perl and ocaml) before being able to run and > use my tool? > > Thanks, > Jon. |
From: Jonathan K. <adv...@gm...> - 2011-12-28 11:17:23
|
Hello World. My apologies for reviving a dead thread, but I wanted to see if anyone else had to do something similar, and how they approached the problem. To reiterate, I am constructing a tool that uses CIL in its workflow: my (Python) code currently runs the "cilly" driver through a system call. I tried the first response that was provided, but I have since realized that "configure" and "make" hardcodes certain paths to my system, so I don't know/think that I will be merely able to include "cilly.asm.exe" or "cilly.byte.exe", or any executable, as part of my tool. I am basically looking for a way to provide the executable without having to include all of the CIL source code, when distributing the tool. If it's not possible, I wouldn't mind having the user configure and make the source code, but I was wondering if it was possible to avoid this extra step for the user. Thanks for any advice, and happy holidays! ~ Jon. On 28 February 2011 00:36, 林楠 <xia...@gm...> wrote: > run make and you will get an executable of your platform > > On Feb 28, 2011 4:08 PM, "Jonathan Kotker" <adv...@gm...> > wrote: > > Hello World. > > > > I am planning to use CIL as part of the research tool that I am writing. > > Currently, my code constructs and runs a system call that runs the cilly > > driver on my local machine, along with specific arguments. My question is > > this: if I were to release the tool as an open-source tool for all to see > > and use, would it be possible to only include the Cilly driver (or a > small > > subset of the CIL files) as part of the files for the tool, or would a > user > > have to install CIL (and thus perl and ocaml) before being able to run > and > > use my tool? > > > > Thanks, > > Jon. > |
From: Mihai T. L. <mt...@gm...> - 2011-12-28 11:57:07
|
On Wed, Dec 28, 2011 at 03:16:46AM -0800, Jonathan Kotker wrote: > I am basically looking for a way to provide the executable without having > to include all of the CIL source code, when distributing the tool. If it's > not possible, I wouldn't mind having the user configure and make the source > code, but I was wondering if it was possible to avoid this extra step for > the user. I see that Fedora distributes a binary package for CIL (ocaml-cil) and one for Cilly (ocaml-cil-cilly). The packages install the usual way, with no sources or compilation. The contents is mostly object files for ocaml-cil RPM and the executables and a few Perl modules for ocaml-cil-cilly RPM. If the end result suits your usage needs you can have a look at the build in the .spec file from the source packages to figure out how to reproduce the install for other package formats or no package at all. :-) Mihai |
From: Gabriel K. <ke...@pp...> - 2011-12-28 14:56:14
|
On Wed, Dec 28, 2011 at 03:16:46AM -0800, Jonathan Kotker wrote: > To reiterate, I am constructing a tool that uses CIL in its workflow: my > (Python) code currently runs the "cilly" driver through a system call. I > tried the first response that was provided, but I have since realized that > "configure" and "make" hardcodes certain paths to my system, so I don't > know/think that I will be merely able to include "cilly.asm.exe" or > "cilly.byte.exe", or any executable, as part of my tool. The cilly (perl) script hardcodes some paths, but cilly.{byte,asm}.exe do not (AFAICT). And the latest release (1.4.0) strives to do the installation in a cleaner way, so you might have a look at it and see if it suits your needs. Do not hesitate to revive old threads or ask more questions :-) Best regards, -- Gabriel |