Re: [coLinux-devel] [PATCH] cobuild.sh-200407.patch

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi George,

nice version. cygwin1.dll was not in the list because I just picked up the
files that are build by cobuild.sh while cygwin1.dll is a binary not build
in the process. The TAP-Network-Driver is also missing for the same
reasons.

I think first step should be to get the patches in the colinux-tree.

After this we can check the location of the patch files from within
cobuild.sh in ../patch (case 1). If we don't find them we step forward
(step 2) and download colinux itself.

The main question I currently have is: where should be the default place
to download/unpack/build the dependent files when we build inside the
colinux-tree?

Cheers,
 Thomas

> This is an minor enhancement on the one that Thomas Fritzsche
> sent earlier.
>
>
>
> 1) it adds cygwin1.dll to the copied files to the newly create
> bin directory
>
> 2) it allows CO_ROOT to be over-ridden.  I did this to keep the
> colinux/bin directory 'clean', and to prepare for tweaking it
> to do an colinux for 2.6 port.
>
>
>
> Dan - I didn't yet have the cobuild.sh reference the patches
> directory for it's patches.  There's a couple issues with this,
> basically we have to decided between something like these two...
>
>
>
> 1) Assume the cobuild.sh is begin run from an bin directory and
> ../patches will get you to the patches.  No sure this is a 'safe'
> or good assumption
>
>
>
> 2) Download and unpack the colinux-*.tar.gz, 'store' where it's
> located.  Then have patches come from CO_SRC/patches directory.
>
>
>
> Unless I'm missing something.
>
>
>
> Thanks,
>
>
>
> George
>
>
>
> -------------------------------------------
>
> Looking for Great Christian Shopping Ideas?
>
> http://www.praize.com/shopping/
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAdQ1bnwJBIFTVIqwRAoc6AJ9tPlN9uap5JAOw3gXhTR8NBKDAwgCgi1NB
54Fifu8P6u+TSkvitDHwPOE=
=lWTo
-----END PGP SIGNATURE-----