By the way, if all that you want to do is to *run* Unicon from Cygwin, please see the updated http://eudyptula.freezope.org/unicon_on_Cygwin , which now includes instructions for that, too.

I have tried to update http://eudyptula.freezope.org/unicon_on_Cygwin to indicate more clearly that when *compiling* Unicon from under Cygwin I was using Clint's toolset (http://www.cs.nmsu.edu/~jeffery/win32/ <http://www.cs.nmsu.edu/%7Ejeffery/win32/>), i.e., his versions of make, cp, and rm, and (importantly) gcc. This generates Unicon executables that are statically linked to the MINGW32 libraries (just like the Windows executables available from Sourceforge) rather than being dynamically linked to the Cygwin DLL; I have not yet succeeded in producing a Cygwin DLL-dependent version of Unicon (and I don't need one at this time. . .).

I have not run Cygwin on XP; I have not demonstrated that you can symlink with Cygwin on XP, though I would be surprised if you cannot.

If Unicon has been fetched from CVS to C:\unicon, then within the Cygwin environment do:

ln -s /cygdrive/c/unicon /usr/local/unicon

Be sure to unzip Clint's tools to /usr/local/unicon in the hierarchy indicated.

Change instances of "cygdrive/d" to "cygdrive/c" in setpath.sh.

After that things should work. Let me know if you persist but encounter problems still.


Larry Bezeau wrote:


Hi Art,

I did receive your message on Unicon and Cygwin both
through the list and personally. Many thanks for the help.
Since then I have tried to compile Unicon under Cygwin and have failed. My setup is somewhat different than yours. I have Windows XP and only a C drive.


I encountered several problems before I quit. The
setpath shell script replaced my original Cygwin path with
a new one that did not include the normal bin directories
containing utilities like make, cp, and rm. This prevented
some make files from functioning properly. I was unsure
about augmenting the path for fear of invoking the wrong
version of the compiler or something like that but I
eventually did. Some of the configuration files seemed to
depend on the exact directory structure including the
presence of a d: drive and I was able to correct some of
these problems but not all of them. My knowledge in this
area is very limited; I was, for example, unaware that
you could symbolically link directories. The final failure I believe was due to not being able to exactly
duplicate your directory structure.


I am hoping that either Icon or Unicon will be officially ported to Cygwin in the near future. I
have a pile of Icon and Unicon programs on Sun
Solaris that I would like to move to Cygwin.


Larry [EMAIL PROTECTED]



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group








-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group

Reply via email to