MinGW - Minimalist GNU for Windows

Keith MARSHALL wrote:

>>I wonder if it exists a script capable of transforming a mingw
>>path to a windows path with respect to the fstab file.
>>
>>For example the script would transform :
>>  /c/foobar         into   c:\foobar
>>  /myMountingPoint  into   c:\foobar\myMountingPoint
>>
>>if one can see "c:\foobar\myMountingPoint /myMountingPoint" in
>>fstab file.
>>    
>>
>
>  (cd /c/foobar && pwd -W)
>
>will give you the Windows path for /c/foobar, IRRESPECTIVE of what
>is in /etc/fstab, PROVIDED /c/foobar exists as a directory.
>
>  awk '$2 == "/c/foobar" { print $1 }' /etc/fstab
>
>will extract the Windows path for /c/foobar's mount point, if it is
>defined in /etc/fstab.
>
>If you want something more robust, which can transform ANY path from
>MSYS to Windows semantics, relative to the MSYS virtual root, even if
>the MSYS path refers to a file, or to a nonexistent directory, here's
>a shell fragment I'm using in my autoconf scripts:
>
><script name=win32path>
> #!/bin/sh
> # Usage: win32path msyspath
> ac_dir="$1"
> pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
> until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
> do
>   ac_dir=`dirname "$ac_dir"`
> done
> ac_dir=`echo "$ac_dir" | sed 's?^[./]*??'`
> ac_val=`echo "$ac_val" | sed 's?/*$??'`
> echo "$1" | sed -e "s?^[./]*$ac_dir/*?$ac_val/?" -e 's?/*$??'
></script>
>
>(Take care with the quoting in that final sed command; the first
> -e expression MUST be in DOUBLE quotes, the second in SINGLE).
>
>You may find these return a Windows path with slashes, rather than
>backslashes, but that's mostly ok -- Windows doesn't care, UNLESS you
>are passing the path to some assinine MS command line application,
>which insists on the backslashes.  In that case, filter the path
>generated by any of the above techniques through "tr / '\\'", e.g.
>
>  (cd /c/foobar && pwd -W) | tr / '\\'
>
>HTH.
>
>Keith.
>
>
>-------------------------------------------------------
>SF.Net email is Sponsored by the Better Software Conference & EXPO September
>19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>_______________________________________________
>Mingw-msys mailing list
>Mingw-msys@...
>https://lists.sourceforge.net/lists/listinfo/mingw-msys
>  
>
Thank you very much everybody!
It fits perfectly my needs for my configure.ac.

Have a nice day
Thierry

Hi All,

Earlier today, I posted the following script:
> <script name=win32path>
>  #!/bin/sh
>  # Usage: win32path msyspath
>  ac_dir="$1"
>  pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
>  until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
>  do
>    ac_dir=`dirname "$ac_dir"`
>  done
>  ac_dir=`echo "$ac_dir" | sed 's?^[./]*??'`
>  ac_val=`echo "$ac_val" | sed 's?/*$??'`
>  echo "$1" | sed -e "s?^[./]*$ac_dir/*?$ac_val/?" -e 's?/*$??'
> </script>

Is there some technical reason why this can't be properly represented
in the SourceForge archive?  All the single quotes in the original are
converted to double quotes in the archive, which rather cripples the
operation of the script, if a user tries to implement it as shown in
the archive.

In this particular example, it is VITAL that SINGLE quotes are used to
wrap the sed substitution expressions on the last two, and preferably
the last three lines, EXCEPT for the first of the pair on the last
line, which MUST be wrapped in DOUBLE quotes.  Elsewhere, the use of
double quotes is correct, as shown in the archive.

What is the best way to post such examples, so that they aren't
damaged in this fashion, in the SourceForge archives?

Regards,
Keith.

> Thank you very much everybody!
> It fits perfectly my needs for my configure.ac.

If you are using this in an autoconf script, you might find my
actual autoconf macro even more useful; (I put it in aclocal.m4,
for each of my projects, so it gets distributed -- it could just
as well go in acsite.m4, for local only use):

<macro name="MSYS_AC_CANONICAL_PATH">
# MSYS_AC_CANONICAL_PATH( VAR, PATHNAME )
# ---------------------------------------
# Set VAR to the canonically resolved absolute equivalent of PATHNAME,
# (which may be a relative path, and need not refer to any existing 
entity).
#
# On Win32-MSYS build hosts, the returned path is resolved to its true
# native Win32 path name, (but with slashes, not backslashes).
#
# On any other system, it is simply the result which would be obtained
# if PATHNAME represented an existing directory, and the pwd command was
# executed in that directory.
#
AC_DEFUN([MSYS_AC_CANONICAL_PATH],
[ac_dir="$2"
 pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
 until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
 do
   ac_dir=`AS_DIRNAME(["$ac_dir"])`
 done
 ac_dir=`echo "$ac_dir" | sed 's?^[[./]]*??'`
 ac_val=`echo "$ac_val" | sed 's?/*$[]??'`
 $1=`echo "$2" | sed "s?^[[./]]*$ac_dir/*?$ac_val/?"'
   s?/*$[]??'`
])
</macro>

Again, take care of the quoting -- the SourceForge archive doesn't
show it correctly!

  -  Backquotes are correct, as shown.
  -  All sed substitutions should be in SINGLE quotes, EXCEPT
     for the first of the pair in the final sed command, which
     MUST be in DOUBLE quotes;  the archive replaces all single
     quotes with double, which breaks the script.
  -  Other than these, DOUBLE quotes are correct.

HTH.

Keith.

Keith MARSHALL wrote:

>>Thank you very much everybody!
>>It fits perfectly my needs for my configure.ac.
>>    
>>
>
>If you are using this in an autoconf script, you might find my
>actual autoconf macro even more useful; (I put it in aclocal.m4,
>for each of my projects, so it gets distributed -- it could just
>as well go in acsite.m4, for local only use):
>
><macro name="MSYS_AC_CANONICAL_PATH">
># MSYS_AC_CANONICAL_PATH( VAR, PATHNAME )
># ---------------------------------------
># Set VAR to the canonically resolved absolute equivalent of PATHNAME,
># (which may be a relative path, and need not refer to any existing 
>entity).
>#
># On Win32-MSYS build hosts, the returned path is resolved to its true
># native Win32 path name, (but with slashes, not backslashes).
>#
># On any other system, it is simply the result which would be obtained
># if PATHNAME represented an existing directory, and the pwd command was
># executed in that directory.
>#
>AC_DEFUN([MSYS_AC_CANONICAL_PATH],
>[ac_dir="$2"
> pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
> until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
> do
>   ac_dir=`AS_DIRNAME(["$ac_dir"])`
> done
> ac_dir=`echo "$ac_dir" | sed 's?^[[./]]*??'`
> ac_val=`echo "$ac_val" | sed 's?/*$[]??'`
> $1=`echo "$2" | sed "s?^[[./]]*$ac_dir/*?$ac_val/?"'
>   s?/*$[]??'`
>])
></macro>
>
>Again, take care of the quoting -- the SourceForge archive doesn't
>show it correctly!
>
>  -  Backquotes are correct, as shown.
>  -  All sed substitutions should be in SINGLE quotes, EXCEPT
>     for the first of the pair in the final sed command, which
>     MUST be in DOUBLE quotes;  the archive replaces all single
>     quotes with double, which breaks the script.
>  -  Other than these, DOUBLE quotes are correct.
>
>HTH.
>
>Keith.
>
>
>-------------------------------------------------------
>SF.Net email is Sponsored by the Better Software Conference & EXPO September
>19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>_______________________________________________
>Mingw-msys mailing list
>Mingw-msys@...
>https://lists.sourceforge.net/lists/listinfo/mingw-msys
>  
>
Thank you again.
I'm not very familiar with m4 macros.
I'll read soon the m4 documentation :)

Thierry

-- 

Thierry Gourdin, AnimatLab
Laboratoire d'Informatique de Paris 6
8, rue du capitaine Scott
75015 PARIS

> Thank you again.
> I'm not very familiar with m4 macros.
> I'll read soon the m4 documentation :)

I'm still learning them myself :)

My MSYS_AC_CANONICAL_PATH macro expands (approximately) to the
code in the win32path script I posted earlier.  Copy and paste
it verbatim, into a file called acsite.m4, in the same place as
your installed autoconf.m4f, (for me that's in the directory
"/usr/share/autoconf/autoconf" in my MSYS tree), and it will be
available to all YOUR configure.ac scripts, OR into a file called
aclocal.m4, in the same directory as configure.ac, to make it
available to just that configure.ac -- (this is best for
distribution, as you can distribute both aclocal.m4 and its
dependent configure.ac along with your project).

Once you've made it available, you can simply use it, by saying
something like:

  MSYS_AC_CANONICAL_PATH([ac_default_prefix], [/mingw])

in configure.ac -- this example makes the default value of the
--prefix=path option to configure resolve to the Win32 native
path to your MinGW tree, without requiring the user to specify
it explicitly.  You could even simplify this further, by also
pasting another macro into acsite.m4 or aclocal.m4:

<macro name="MSYS_AC_PREFIX_DEFAULT">
# MSYS_AC_PREFIX_DEFAULT( PREFIX )
# --------------------------------
# Like standard AC_PREFIX_DEFAULT( PREFIX ), but resolves the assigned
# path using the MSYS_AC_CANONICAL_PATH macro, (defined below).
#
# (Ideally, autoconf should always define "ac_default_prefix" this way,
#  but, for all autoconf versions to date, we need to force it).
#
AC_DEFUN([MSYS_AC_PREFIX_DEFAULT],
[MSYS_AC_CANONICAL_PATH([ac_default_prefix],[$1])dnl
])
</macro>

and then make your configure.ac begin like:

  AC_INIT
  MSYS_AC_PREFIX_DEFAULT([/mingw])
  :
  :

BTW, I've written MSYS_AC_CANONICAL_PATH so that it will leave a POSIX
path name untouched on any non-MSYS platform, so it can be used in ANY
configure.ac, which is written with portability in mind.  However,

  MSYS_AC_PREFIX_DEFAULT([/mingw])

isn't a good idea for portability -- better to use

  AC_INIT
  MSYS_AC_PREFIX_DEFAULT([/usr/local])
  :

which preserves the default autoconf behaviour for non-MSYS platforms,
but maps the default prefix to the native Win32 representation of
/usr/local, (for me this becomes D:/MSYS/1.0/local), when you build
on an MSYS platform.  One caveat however -- a standard MSYS install
DOESN'T create a /usr/local directory, so you need to mkdir it for
yourself, if you intend to use it -- a STANDARD autotool scripted
build WON'T do that for you, and will fail if the installation path
doesn't exist, when you do the "make install"; (you could, of course,
script a check in configure.ac, and arrange for configure to do the
appropriate mkdir, if necessary, but that isn't normal practice,
and may not be generally desirable).

HTH.

Keith.

On 12:37:26 pm 2005-07-28 Keith MARSHALL <keith.marshall@...> wrote:
> Hi All,
>
> Earlier today, I posted the following script:
> >  <script name=win32path>
> >   #!/bin/sh
> >   # Usage: win32path msyspath
> >   ac_dir="$1"
> >   pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
> >   until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
> >   do
> >     ac_dir=`dirname "$ac_dir"`
> >   done
> >   ac_dir=`echo "$ac_dir" | sed 's?^[./]*??'`
> >   ac_val=`echo "$ac_val" | sed 's?/*$??'`
> >   echo "$1" | sed -e "s?^[./]*$ac_dir/*?$ac_val/?" -e 's?/*$??'
> >  </script>
>
> Is there some technical reason why this can't be properly represented
> in the SourceForge archive?  All the single quotes in the original are
> converted to double quotes in the archive, which rather cripples the
> operation of the script, if a user tries to implement it as shown in
> the archive.
>

Open a support request to SF.

Earnie

Earnie Boyd wrote, quoting me:
>> Hi All,
>>
>> Earlier today, I posted the following script:
>> >  <script name=win32path>
>> >   #!/bin/sh
>> >   # Usage: win32path msyspath
>> >   ac_dir="$1"
>> >   pwd -W >/dev/null 2>&1 && ac_pwd_w="pwd -W" || ac_pwd_w=pwd
>> >   until ac_val=`exec 2>/dev/null; cd "$ac_dir" && $ac_pwd_w`
>> >   do
>> >     ac_dir=`dirname "$ac_dir"`
>> >   done
>> >   ac_dir=`echo "$ac_dir" | sed 's?^[./]*??'`
>> >   ac_val=`echo "$ac_val" | sed 's?/*$??'`
>> >   echo "$1" | sed -e "s?^[./]*$ac_dir/*?$ac_val/?" -e 's?/*$??'
>> >  </script>
>>
>> Is there some technical reason why this can't be properly represented
>> in the SourceForge archive?  All the single quotes in the original are
>> converted to double quotes in the archive, which rather cripples the
>> operation of the script, if a user tries to implement it as shown in
>> the archive.
>>
>
> Open a support request to SF.

Done.  It's item 1247307 on the SF Support Tracker, for anyone who may
be interested.

Regards,
Keith.