Re: Packing a C# project.

2008/6/23 Isak Savo <[email protected]>:

> On Sun, Jun 22, 2008 at 2:18 PM, Neil Munro <[email protected]> wrote:
> >
> >
> > May I ask if you've had chance to look at my file yet?
>
> Thanks for the reminder .. totally forgot :-)
>
> Took a quick peek and here's some feedback:
>
> > SoftwareVersion: 0.1.6
> > # SoftwareVersion: @VERSION@
>
> You can use the latter, and the configure script will replace
> @VERSION@ with the version specified in the build tools. This way,
> when you do a new release, you don't have to update the version in the
> .apspec.


I need to learn how to make MonoDevelop pass the correct version number to
the configure script, I stuck the actual version there as a quick work
around.


>
>
> > [BuildPrepare]
> > # For ./configure based systems this is a good default
> > ./install $build_root
> > #prepareBuild --with-some-feature
> > prepareBuild
>
> We discussed this before, but I'll bring it up again. If monodevelop
> has generated makefiles + configure script, then (I don't think) you
> need the install script.
> And of course, the other way around is true: if you use the install
> script, then you don't need to have monodevelop create the
> makefiles+configure script. (unless you want them for some other
> reason, like distributing in source form to non-monodevelop users)


Ok, prepareBuild it is!

>
>
> > [Prepare]
> > # Dependency checking
> > require @mono-project.com/mono 1.2.6
>
> This is correct, but will not work with the current (or any) version
> of autopackage since I haven't added support for it yet. :-(
>
> I've created a temporary skeleton that will let you do:
>  requireAtLeast @mono-project.com/mono:1.2.6
> if any 1.2.x version will do for you, then you can do:
>  requireAtLeast @mono-project.com/mono:1.2.6
>
> This works agains the software version (i.e. the version number you
> see on mono-project.com) and not the actual .NET profile version (like
> .NET 1.0, 1.1, 2.0 which are the versions defined by microsoft).


Sure, that makes sense. The autopackage i tried failed, might be because of
this. Will adjust and try again.

>
>
> Just extract the attached tarball to your autopackage/ directory and
> try it. (to be honest, I don't remember the directory layout for
> bundled skeletons... if someone else on the list has done this, speak
> up :)


Will have a play :)

>
>
> > [Install]
> > installExe bin/*
>
> Is the binary all you ship? No data files, docs, libraries, icons, etc.?


Only the help.txt file, but I am not entirely sure how to install it. I
guess it's a data file, so installData share/*?

>
>
> -Isak
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
> For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
>