Okay, so the idea of the mingw32ce developers was that they are
building on Cygwin (the name 'mingw' makes that a little more
difficult to realize - it seems like some ping-pong chain of
development steps).

Cygwin is needed to *use* the package (cygwin1.dll), plus Cygwin
is also able to properly unpack the package, simply by issuing
standard 'tar -zxvf <fn>' command.

I'll include Cygwin dependency and these small instructions in the
README placeholder in mingwarm dir:

---
Download package from here and unpack into this directory:

https://sourceforge.net/project/downloading.php?group_id=173455&use_mirror=switch&filename=cygwin-cegcc-mingw32ce-0.51.0-1.tar.gz&a=34126466

NOTES: - In order to unpack and use this package, you'll
         need Cygwin package (from http://cygwin.com) installed
         and put in PATH for Cygwin runtime (cygwin1.dll).
       - To unpack:
            > sh
            $ tar -zxvf cygwin-cegcc-mingw32ce-0.51.0-1.tar.gz
            $ exit
       - Move content of /opt/mingw32ce directory to this one.
---

Brgds,
Viktor

On Mon, Jun 8, 2009 at 2:29 PM, Viktor Szakáts<[email protected]> wrote:
>>> Now I cannot recommend in a Windows package to use a *nix system
>>> to unpack it, so I'm looking for free tools which are able to unpack this
>>> file properly.
>>> Any ideas?
>>
>> Can you define what "properly" means for you when soft and hard links are
>> unpacked in Windows on file system which does not support them?
>
> I described it. Properly means that the resulting directory is
> 136MB in size. That also means no zero length files are present
> in the tree (as placeholders for links).
>
> One such file is actually the GCC executable which we need
> to call from GNU Make and hbmk2:
>
> opt\mingw32ce\bin\arm-wince-mingw32ce-gcc.exe
>
> it's zero length with these tools, but should be 360474 bytes.
>
> It's a little bit hard to understand why mingw32ce developers
> thought it a good idea to distribute a Windows package which
> cannot be unpacked on Windows...
>
> If I'm asking for the impossible I'll have to either drop mingwarm
> option from the final builds or include mingw32ce in our package.
> I don't really like any of these options :(
>
> Brgds,
> Viktor
>
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to