* Re: Getting simple STL program to compile
@ 1999-09-23 6:17 Earnie Boyd
1999-09-23 6:44 ` Using Microsoft Visual C David Most
1999-09-30 23:42 ` Getting simple STL program to compile Earnie Boyd
0 siblings, 2 replies; 6+ messages in thread
From: Earnie Boyd @ 1999-09-23 6:17 UTC (permalink / raw)
To: Clark Sims, cygwin users
--- Clark Sims <clarksimsgnu@my-Deja.com> wrote:
-8<-
> Where can I download mingw32-gcc-2.95?
>
From Mumit's site. URL pointer on my page.
>
> >build it with no problems. I copied cygwin to another directory tree,
> removed
> >the compiler and bin-utilities, removed the lib and include directories,
> then
> >added the mingw32 versions of what I removed. I prefer this structure when
>
>
> Isn't this basicly the whole compiler. Wouldn't it have been easier to just
> change the path? Why download cygwin at all?
>
Yes it is the "whole" compiler. I use cygwin for the UNIXy feel. I have to
use both so being able to do `ls /some/directory' is pleasant. The way I have
things structured I can test different scenarios of cygwin environments without
having to bother other scenarios. All I have to do is change where / points
and everything else is configured. I can do this in a .bat file that I can
shortcut to the desktop and choose at will the environment I want to use (only
one at a time though).
>
> >building native programs. I also have a boot.bat file that does an
> effective
> >change root by doing a sh -c 'cd bin && ./umount / && ./mount
> d:\\root\mingw32
> >/' before starting bash. I also create and copy a more normalized directory
> >tree which allows cygwin to be more friendly to non-cygwin programs.
> >
>
> What is the point of this?
> Is it so /include appears where so many other Unix program expect it to
> appear?
> I guess you could acheive the samething by
> ln -s //d/root/mingw32/h /h
>
Yes. I like /usr/include to be where it is supposed to be.
>
> >I've never had the problems people have with using -mno-cygwin.
>
>
> Glad to hear it. I am glad that you got this program to compile :-)
>
> Thanks again,
You're welcome. BTW, I did see Mumit's response to this and to his defense I
have to say the "cygwin" doesn't include "conio.h" because "cygwin" is an
ANSI/POSIX system. However, the windows headers are included and the gcc
compiler environment is supporting both methods. The problem really is how the
files are located and when you try to mix "cygwin" and "mingw32" the compiler
has to be able to find the correct headers and _YOU_ have to tell it where to
find them. I choose to avoid the problem, I don't mix the two.
Hmm. I just had a brainstorm idea, I wonder if it would help to have a
directory structure of:
include/cygwin/<posix_headers>
include/mingw32/<windows_headers>
lib/cygwin/<cygwin_libraries>
lib/mingw32/<windows_libraries>
as opposed to:
include/<posix_headers>
include/mingw32/<windows_headers>
lib/<cygwin_libraries>
lib/mingw32/<windows_libraries>
Mumit, what do you think? Would it help to segregate the two independant
headers/libraries from the compiler perspective?
=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Using Microsoft Visual C
1999-09-23 6:17 Getting simple STL program to compile Earnie Boyd
@ 1999-09-23 6:44 ` David Most
1999-09-23 11:12 ` Mumit Khan
1999-09-30 23:42 ` David Most
1999-09-30 23:42 ` Getting simple STL program to compile Earnie Boyd
1 sibling, 2 replies; 6+ messages in thread
From: David Most @ 1999-09-23 6:44 UTC (permalink / raw)
To: cygwin users
I'm working on a project which is a mix of UNIX and Windows. A large
portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in
Win32.
I would like to get migrate the project from cygwin/gcc to MSVC. Ideally,
I'd simply point the compiler at the cygwin unix headers and link to the
cygwin DLL. Has anyone attempted this with success? Do you have any tips
for me? Am I on the right track (not referring to the migration towards
windows <g>)?
Thanks in advance,
Dave
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Using Microsoft Visual C
1999-09-23 6:44 ` Using Microsoft Visual C David Most
@ 1999-09-23 11:12 ` Mumit Khan
1999-09-30 23:42 ` Mumit Khan
1999-09-30 23:42 ` David Most
1 sibling, 1 reply; 6+ messages in thread
From: Mumit Khan @ 1999-09-23 11:12 UTC (permalink / raw)
To: David Most; +Cc: cygwin users
David Most <dmost@ascend.com> writes:
> I'm working on a project which is a mix of UNIX and Windows. A large
> portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in
> Win32.
>
> I would like to get migrate the project from cygwin/gcc to MSVC. Ideally,
> I'd simply point the compiler at the cygwin unix headers and link to the
> cygwin DLL. Has anyone attempted this with success? Do you have any tips
> for me? Am I on the right track (not referring to the migration towards
> windows <g>)?
You may be able to do this, but may run into problems with the linking
to libcygwin.a, which is not quite compatible to what MSVC linker expects.
In the future, when GNU as/ld is completely PE compatible, it should work
in theory. If you want to experiment, I suggest rebuilding the import
library using LIB.EXE (or whatever MSVC uses), add back the static archive
objects into the import library and see how things go.
I doubt if anyone's tried this yet, so it's up to you.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Using Microsoft Visual C
1999-09-23 6:44 ` Using Microsoft Visual C David Most
1999-09-23 11:12 ` Mumit Khan
@ 1999-09-30 23:42 ` David Most
1 sibling, 0 replies; 6+ messages in thread
From: David Most @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin users
I'm working on a project which is a mix of UNIX and Windows. A large
portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in
Win32.
I would like to get migrate the project from cygwin/gcc to MSVC. Ideally,
I'd simply point the compiler at the cygwin unix headers and link to the
cygwin DLL. Has anyone attempted this with success? Do you have any tips
for me? Am I on the right track (not referring to the migration towards
windows <g>)?
Thanks in advance,
Dave
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting simple STL program to compile
1999-09-23 6:17 Getting simple STL program to compile Earnie Boyd
1999-09-23 6:44 ` Using Microsoft Visual C David Most
@ 1999-09-30 23:42 ` Earnie Boyd
1 sibling, 0 replies; 6+ messages in thread
From: Earnie Boyd @ 1999-09-30 23:42 UTC (permalink / raw)
To: Clark Sims, cygwin users
--- Clark Sims <clarksimsgnu@my-Deja.com> wrote:
-8<-
> Where can I download mingw32-gcc-2.95?
>
From Mumit's site. URL pointer on my page.
>
> >build it with no problems. I copied cygwin to another directory tree,
> removed
> >the compiler and bin-utilities, removed the lib and include directories,
> then
> >added the mingw32 versions of what I removed. I prefer this structure when
>
>
> Isn't this basicly the whole compiler. Wouldn't it have been easier to just
> change the path? Why download cygwin at all?
>
Yes it is the "whole" compiler. I use cygwin for the UNIXy feel. I have to
use both so being able to do `ls /some/directory' is pleasant. The way I have
things structured I can test different scenarios of cygwin environments without
having to bother other scenarios. All I have to do is change where / points
and everything else is configured. I can do this in a .bat file that I can
shortcut to the desktop and choose at will the environment I want to use (only
one at a time though).
>
> >building native programs. I also have a boot.bat file that does an
> effective
> >change root by doing a sh -c 'cd bin && ./umount / && ./mount
> d:\\root\mingw32
> >/' before starting bash. I also create and copy a more normalized directory
> >tree which allows cygwin to be more friendly to non-cygwin programs.
> >
>
> What is the point of this?
> Is it so /include appears where so many other Unix program expect it to
> appear?
> I guess you could acheive the samething by
> ln -s //d/root/mingw32/h /h
>
Yes. I like /usr/include to be where it is supposed to be.
>
> >I've never had the problems people have with using -mno-cygwin.
>
>
> Glad to hear it. I am glad that you got this program to compile :-)
>
> Thanks again,
You're welcome. BTW, I did see Mumit's response to this and to his defense I
have to say the "cygwin" doesn't include "conio.h" because "cygwin" is an
ANSI/POSIX system. However, the windows headers are included and the gcc
compiler environment is supporting both methods. The problem really is how the
files are located and when you try to mix "cygwin" and "mingw32" the compiler
has to be able to find the correct headers and _YOU_ have to tell it where to
find them. I choose to avoid the problem, I don't mix the two.
Hmm. I just had a brainstorm idea, I wonder if it would help to have a
directory structure of:
include/cygwin/<posix_headers>
include/mingw32/<windows_headers>
lib/cygwin/<cygwin_libraries>
lib/mingw32/<windows_libraries>
as opposed to:
include/<posix_headers>
include/mingw32/<windows_headers>
lib/<cygwin_libraries>
lib/mingw32/<windows_libraries>
Mumit, what do you think? Would it help to segregate the two independant
headers/libraries from the compiler perspective?
=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Using Microsoft Visual C
1999-09-23 11:12 ` Mumit Khan
@ 1999-09-30 23:42 ` Mumit Khan
0 siblings, 0 replies; 6+ messages in thread
From: Mumit Khan @ 1999-09-30 23:42 UTC (permalink / raw)
To: David Most; +Cc: cygwin users
David Most <dmost@ascend.com> writes:
> I'm working on a project which is a mix of UNIX and Windows. A large
> portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in
> Win32.
>
> I would like to get migrate the project from cygwin/gcc to MSVC. Ideally,
> I'd simply point the compiler at the cygwin unix headers and link to the
> cygwin DLL. Has anyone attempted this with success? Do you have any tips
> for me? Am I on the right track (not referring to the migration towards
> windows <g>)?
You may be able to do this, but may run into problems with the linking
to libcygwin.a, which is not quite compatible to what MSVC linker expects.
In the future, when GNU as/ld is completely PE compatible, it should work
in theory. If you want to experiment, I suggest rebuilding the import
library using LIB.EXE (or whatever MSVC uses), add back the static archive
objects into the import library and see how things go.
I doubt if anyone's tried this yet, so it's up to you.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-09-30 23:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-09-23 6:17 Getting simple STL program to compile Earnie Boyd
1999-09-23 6:44 ` Using Microsoft Visual C David Most
1999-09-23 11:12 ` Mumit Khan
1999-09-30 23:42 ` Mumit Khan
1999-09-30 23:42 ` David Most
1999-09-30 23:42 ` Getting simple STL program to compile Earnie Boyd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).