To clarify my intent: The target users of my tool will be using Windows,
and as I already have compiled CIL for my own purposes, I wanted users to
be able to use the core necessary files, without having to recompile all of
CIL. (This would, among other things, impose extra requirements for my
tool.)
Currently, I'm including the following files as part of my tool:
cil/LICENSE
cil/bin/CilConfig.pm
cil/bin/cilly
cil/bin/cilly.bat
cil/lib/*.pm
cil/obj/.depend/inliner.*
cil/obj/.depend/loopHandler.*
cil/obj/x86_WIN32/cilly.*
cil/obj/x86_WIN32/inliner.*
cil/obj/x86_WIN32/loopHandler.*
where inliner is the CIL inliner, and loopHandler is a CIL extension that I
wrote. I have a configuration script that edits the hard-coded paths in
cil/bin/CilConfig.pm and cil/bin/cilly.bat to match the user system.
Is there anything else I should be including? The above files seem to be
the only ones the tool needs. Or is there a better way to go about this
entire process?
For what it's worth, my tool will be released under the modified BSD
license.
Thanks for any help and suggestions,
Jon.
On 11 January 2013 16:21, Jonathan Kotker <advancedvers...@gmail.com> wrote:
> Hello (CIL) World.
>
> I have a question about including CIL as part of a tool and tool release:
> What is the conventional method for including CIL as part of a tool release?
>
> By this, I mean: if a tool uses CIL, does the tool release include the
> entire CIL source code? The one downside I can see to this is that it
> requires the package to include the whole source code redundantly, when it
> can be downloaded separately. However, an upside would be that the user can
> compile CIL on their own system, and all the hard-coded paths in the Perl
> scripts would be relevant to the particular machine.
>
> Alternatively, I was experimenting with the idea of distributing only the
> Cilly driver and the files that it depends on, along with the code, since
> my code only depends on the Cilly driver. The one downside that I see to
> this is that the driver and the object files will be machine-dependent;
> another downside is that I will have to write code that modifies the
> hard-coded paths in the driver.
>
> I suppose I could also ask the user to install Cilly on her own, and move
> it to a particular directory, but I would like to make the process as
> seamless and "one-command-does-everything" as possible.
>
> Suggestions, comments and questions are very welcome.
>
> Thanks!
> ~ Jon.
>
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
CIL-users mailing list
CIL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cil-users
