dominik wrote:

> dmd for 64bit, windows atleast, since gdc and windows is a no go - please!

How about dmd 64 bit linux?  I'm still waiting for this.

"Bill Baxter" <dnewsgroup@billbaxter.com> wrote in message news:ftvis4$2v9s$1@digitalmars.com...
>
> I think the problem with Vista is that just that Microsoft finally got things right pretty much right at last with XP in terms of the OS.  It was the first time Win95 and WinNT really were integrated.  And that was a big deal.  This time all they've got to encourage people to switch is glitz and hype.  That's not enough to impress the folks in corporate IT centers with the big budgets.  XP works pretty darn well.  That's the biggest problem with Vista.

Completely agreed.

I don't know if it's telling or not, but Windows 7 is possibly slated for release sometime in the next year (http://www.news.com/8301-13860_3-9911470-56.html).  Like the article says that might just be a developer release.  Even if it's not, it's supposed to come out in 2010 or so.  That seems terribly quick, and I'm not sure if it's just MS being MS or if they really realized what an unattractive OS Vista is for most people.

Lionello Lunesu wrote:
> dominik wrote:
>> Lionello Lunesu Wrote:
>>> I never got mingw to work, but cygwin worked fine. Just make sure you install all needed headers/libraries to build GCC/GDC and it'll work, I promise ;)
>> 
>> So if I install cygwin and mingw I should be able to compile gcc/gdc then? I don't wan't to make cygwin dependable executables though :\
> 
> You don't need mingw if you have cygwin. At least, I just installed cygwin and that's all I needed.
> 
> I don't think the executables need cygwin, just GDC and GCC need cygwin.

This is the wrong way to go.  Cygwin compiled executables definitely need cygwin to run!  When you're running something under cygwin you're actually running an app that is using a windows port of the linux programming APIs.  If you compile an app using gcc under cygwin you're explicitly linking it to the cygwin environment.

Yeah you can still redistribute it, but you'll need to distribute the appropriate cygwin dll's and so forth along with your app.

mingw and gdc win (http://gdcwin.sourceforge.net/) are really what he wants.  I've been using mingw and gdcwin to create binary redistributable windows apps for some time now (yes with Tango), without any issues what-so-ever.

Dominik, if you have any specific problems, maybe we can help you sort them out.

Tim.

Tim Burrell Wrote:
> Dominik, if you have any specific problems, maybe we can help you sort them out.

well the problem right now is that I don't know what I have to get and what I have to do in order to have gdc (with Tango) on my windows box for both 32bit and 64bit compilation. It is not imperative that I have both 32 and 64bit on 32bit box, I can have 32bit on 32bit OS and 64bit on 64bit OS, it doesn't matter. I just can't find out what I have to download and how to install/compile GDC by myself in order to use GDC on Windows, since I have no experience with gcc.

Do I download mingw, do I also download MSYS, do I download them in binary or in source, what then? What version of GCC is that then? Can I use latest gcc somehow etc.. lots of questions :)

On Mon, Apr 14, 2008 at 3:56 PM, Tim Burrell <tim@timburrell.net> wrote:
>  This is the wrong way to go.  Cygwin compiled executables definitely need
> cygwin to run!  When you're running something under cygwin you're actually
> running an app that is using a windows port of the linux programming APIs.
> If you compile an app using gcc under cygwin you're explicitly linking it to
> the cygwin environment.
>
>  Yeah you can still redistribute it, but you'll need to distribute the
> appropriate cygwin dll's and so forth along with your app.
>
>  mingw and gdc win (http://gdcwin.sourceforge.net/) are really what he
> wants.  I've been using mingw and gdcwin to create binary redistributable
> windows apps for some time now (yes with Tango), without any issues
> what-so-ever.
>
>  Dominik, if you have any specific problems, maybe we can help you sort them
> out.
>
>  Tim.
>

I believe you can pass -mno-cygwin to make it use the mingw stuff instead.

Anders

dominik a écrit :
> Tim Burrell Wrote:
>> Dominik, if you have any specific problems, maybe we can help you sort them out.
> 
> well the problem right now is that I don't know what I have to get and what I have to do in order to have gdc (with Tango) on my windows box for both 32bit and 64bit compilation. It is not imperative that I have both 32 and 64bit on 32bit box, I can have 32bit on 32bit OS and 64bit on 64bit OS, it doesn't matter. I just can't find out what I have to download and how to install/compile GDC by myself in order to use GDC on Windows, since I have no experience with gcc.

Last time I checked, it was not possible to build 64-bit applications using MinGW. The MinGW developers are working on it though.

I don't think there is any way to output 64-bit code for Windows at the moment.

== Quote from e-t172 (e-t172@akegroup.org)'s article
> dominik a écrit :
> > Tim Burrell Wrote:
> >> Dominik, if you have any specific problems, maybe we can help you sort them out.
> >
> > well the problem right now is that I don't know what I have to get and what I have to do in order to
have gdc (with Tango) on my windows box for both 32bit and 64bit compilation. It is not imperative
that I have both 32 and 64bit on 32bit box, I can have 32bit on 32bit OS and 64bit on 64bit OS, it
doesn't matter. I just can't find out what I have to download and how to install/compile GDC by myself in
order to use GDC on Windows, since I have no experience with gcc.
> Last time I checked, it was not possible to build 64-bit applications
> using MinGW. The MinGW developers are working on it though.
> I don't think there is any way to output 64-bit code for Windows at the
> moment.

In theory, LLVMDC should be able to do this.  Here's the link:

http://www.dsource.org/projects/llvmdc

And frankly, given the slow progress of GDC recently, I'm starting to think that it may be the preferred alternative D compiler anyway.  I'll be very excited once it's production-quality.


Sean

"e-t172" <e-t172@akegroup.org> wrote in message news:fu022q$17nh$1@digitalmars.com...
> I don't think there is any way to output 64-bit code for Windows at the moment.

oh damn :|

"Sean Kelly" <sean@invisibleduck.org> wrote in message news:fu053o$1e16$1@digitalmars.com...
> In theory, LLVMDC should be able to do this.  Here's the link:
>
> http://www.dsource.org/projects/llvmdc
>
> And frankly, given the slow progress of GDC recently, I'm starting to
> think
> that it may be the preferred alternative D compiler anyway.  I'll be very
> excited once it's production-quality.

oh lots of work still to do there, oh damn all of the tickets are beyond my scope :|

Bill Baxter wrote:
> I think the problem with Vista is that just that Microsoft finally got things right pretty much right at last with XP in terms of the OS.  It was the first time Win95 and WinNT really were integrated.  And that was a big deal.  This time all they've got to encourage people to switch is glitz and hype.  That's not enough to impress the folks in corporate IT centers with the big budgets.  XP works pretty darn well.  That's the biggest problem with Vista.
> 
> --bb

No they didn't. The big thing that Vista adds that XP/Server 03 didn't have is kernel security (and integrated OneCare, and that funny desktop search thing, and...). For people who know how to use it right (for example my dad just clicks accept on anything), it's a far more secure solution than anything any other OS has.