GTK Build from source

On Aug 20, 3:47 pm, Simon Wright <simon.j.wri...@mac.com> wrote:
> "RasikaSriniva...@gmail.com" <RasikaSriniva...@gmail.com> writes:
> > In any case, I found that on Windows for gnat based development, I am
> > not sure cygwin works that well. for example, the -I and other such
> > specifications want to interpret the argument using the native
> > directory separator ie "\" and not the unix like "/"
>
> I prefer not to use -I etc; leave that sort of thig up to gnatmake,
> which it does perfectly well.
>
> You can of course have other problems using mixed Windows/Cygwin tools,
> in our case with environment variables most of which get converted
> properly by cygwin from the Windows set, but (if I remember correctly)
> not tools such as gnatmake which don't understand /cygdrive/d/... and
> need d:/... instead.
>
> What we did was to get a tool to create .reg and .sh (and .el!) files
> with equivalent and appropriate meanings: then you can double-click on
> the .reg file for use on command shells, and thereafter source the .sh
> file for cygwin shells from ~/.profile. A PITA to set up, but invisible
> after it's done.

thanks for all interesting ideas. srini

Stephen,

> Also, installing Cygwin at c:/ (_not_ c:/cygwin) makes things _much_
> nicer; then windows c:/foo/bar is the _same_ as cygwin /foo/bar; no
> /cygdrive/c/ or `cygpath -w /foo/bar' necessary. The Cygwin installer
> complains when you do this; that's because it assumes you don't know
> what you are doing, and might have some other bin directory at c:/bin.
> Ignore the complaint!

This is true, but I hate having lot of dir on my top level C drive. My
configuration is:

- I install Cygwin into c:\cygwin

- I mount my working directories:

$ mount c:\\home /home
$ mount c:\\opt /opt

As all my work is done into my home directory (/home/obry) no problem
either with /cygdrive/c or whatever. As I install some stuff on /opt the
mount point makes this possible too.

There is one single rule to follow for directories that must be accessed
by Cygwin and standard Windows applications (ming based compiler for
example):

-> those directories must be accessed using an equivalent PATH

c:\whatever must be equivalent to /whatever

So mount points are quite handy there.

> Not me!

Likewise! cmd.exe is junk for developers.

Pascal.

--

--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

Simon,

> You can of course have other problems using mixed Windows/Cygwin tools,
> in our case with environment variables most of which get converted
> properly by cygwin from the Windows set, but (if I remember correctly)
> not tools such as gnatmake which don't understand /cygdrive/d/... and
> need d:/... instead.

Right, GNAT is a ming based applications (using native Windows
interface) so /cygdrive/d cannot be understood as this is Cygwin stuff.

Pascal.

--

--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

On Aug 19, 7:43*pm, Martin <martin.do...@btopenworld.com> wrote:
> I have to admit I find the whole "preprocessing" steps really
> annoying...
[snip]
> Of course portability is great and that preprocessing can be a better
> way of achieving it than other means but couldn't there be simple pre-
> built versions for say just Wintel and Linux/x86 - surely that would
> cover 95% of users of these "libre" versions?

Just checking the AWS list and it would seem that a large percentage
of questions are build problems...