This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [bigloo] Setting up Emacs to work with Bigloo
- From: Alex Goldman <alex dot gman at gmail dot com>
- To: Jeremy Shute <shutej at crazilocks dot com>, cygwin at cygwin dot com
- Date: Thu, 21 Jul 2005 14:40:39 -0700
- Subject: Re: [bigloo] Setting up Emacs to work with Bigloo
- References: <9bbd2794050721085031f01b9b@mail.gmail.com> <42DFEF0F.4080902@crazilocks.com>
- Reply-to: Alex Goldman <alex dot gman at gmail dot com>
On 7/21/05, Jeremy Shute <shutej@crazilocks.com> wrote:
> My figuring is: yes, you could install with all Microsoft tools and
> NTEmacs (and yes, that's the "ideal" way to go about it), but you can
> always postpone that after you've hacked a nice large codebase.
>
> You can always use Yannis' install right out of the box to build
> everything if you need commercial distribution. For development,
> sticking to Cygwin may violate your morale, but hey. It gets the job done.
Doesn't this open a whole new can of worms?
* linking to windows libraries
* environments
* compilation management (makefiles on Cygwin and some script for Windows) ?
> I HAVE dropped in the free Microsoft compilers with a simple batch
> file. See my web page (crazilocks.com) for details. They're out of
> date, but something similar will work.
Thanks, although I have already gotten to the point where `bigloo
hello_world.scm` works (at a great expense of man-hours that could be
more useful elsewhere, I must say, and I had to give up on compiling
bigloo from sources)
> Remember that Bee makes little sense in the case of Windows-only
> environments, anyway.
The debugger doesn't work either?
> Windows doesn't have GNU Make. (One of the best
> reasons to use Bee!!!) If you're talking MinGW, maybe it's a different
> story.
For Bigloo programmers, what does MS Visual Studio IDE offer?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/