Re: [Tinycc-devel] TinyCC-Win32 Port Created on Sf.net

[Fabrice Bellard]

I agree that a second project just for porting TinyCC to win32 is not 
worthwhile. I hope this is a temporary solution. As I said some time ago 
to Thomas, I agree to include patches for win32 into TinyCC provided 
they are not too intrusive. I also clearly prefer using the MinGW tools 
instead of Visual C++. I can also put links to win32 executables 
directly on the TinyCC web page, as I do for the Debian and Redhat packages.

Note that there is already a win32 target for TinyCC (tcc.exe in the 
Makefile). I am not testing it very often, but it used to work, at least 
to generate code in memory. Using MSYS and MinGW, TinyCC should be 
easily compilable in a Windows environment.

Fabrice.

Charlie Gordon wrote:
> This is a sad decision!
> Why split a project just for the sake of porting it to Windows ?
> Why can't you just add the necessary features to the existing project ?
> It is going to be very difficult to keep both projects in sync !
> Why did Fabrice not respond and object to this ?
> Take after the Lucid emacs split : jwz did this just to make a stable
> version ship... It quickly became impossible to resync, and now has become a
> major religious schism (this is the XEmacs story).
> Are you planning to duplicate tinycc source tree or just extend it with Gui
> and tools extensions ?
> Please don't do it!
> Fabrice please react to this!
>
> Charlie Gordon.
>
> ----- Original Message -----
> From: "Thomas Harning Jr." <address@hidden>
> To: <address@hidden>
> Sent: Monday, October 13, 2003 3:28 AM
> Subject: [Tinycc-devel] TinyCC-Win32 Port Created on Sf.net
>
>
>
> > To all Win32 TinyCC desirers, the port to Win32 has its own Sourceforge
> > project.
> > http://www.sf.net/projects/tinycc-win32 is the root project page
> > http://tinycc-win32.sf.net has not been set up yet since I have been
> > working to create a release.
> > The release should be up ASAP as I have created 1 example and have ported
> > TinyCC to run and compile with VC 7.1
> > The patch for the TCC 0.9.20 will also be generated ASAP to follow through
> > with the GNU license requirements that the original TCC has.
> >
> > Any developers wanting to join the Dev-team for TinyCC-Win32, please email
> > me and try to include any work you've done so far, ideas, and previous
> > experience.  Please to not try to join if you have no idea what you are
>
> doing.
>
> > Notes on progress for this coming release:
> >  - only compiles to memory
> >  - no bounds checking
> >  - no debug data
> >  - no lib,dll includes really...  .a and .o includes that are in ELF
> > format MIGHT work, since tcclib1.a worked before.
> >  - tcclib1.a removed from requirements, since software math isn't exactly
> > needed [yet?]
> >  - almost a pure port, so some bugs may be present in addition to
> > pre-existing bugs ...
> >
> > For everyone, even/especially non-devs, if you have any patch/code that
> > could make any of these features work properly, please get the release and
> > send me a patch, or just give me the patch since i have a special
>
> DIFF-type
>
> > program that can work with 3 different file versions.  I hope to see this
> > Win32 version flourish and have full .exe, .obj, .lib, .dll file
> > generation/include capabilities so that this can be a super-tool for
> > script-tool users, since they might know C already, and the compiled form
> > of the runnable program is very nice as opposed to interpretted code.
> >
> >
> >
> > _______________________________________________
> > Tinycc-devel mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/tinycc-devel
>
>
>
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/tinycc-devel