Re: Nasm 0.99.01 available

Jim Carlock wrote:
"Frank Kotler" wrote...
: Absolutely! And if you understand what you see, contribute! Nasm is
: "user maintained". The Original Authors have withdrawn from the
: battlefield (do you suppose they know something?). Be thankful that
: there are people far more knowledgeable than I involved - things could
: be a lot worse!

If I wanted to compile it myself, there a quick list of steps to follow
through anywhere if I'm using VC6 (aka VS98/VC98)? I have Perl
installed, just need to run a batch file to get it operable inside of a
command prompt.

If you've got a CVS checkout, you'll need Perl. For a "release" source package, you shouldn't - unless you want to change something. The Perl-generated files are in the distribution. You *should* be able to do "make -f Mkfiles\Makefile.vc" and just stand back and watch in bemused wonderment. Since 0.99.xx is in a somewhat "unstable" state, this might not happen. With 0.99.00, you would have had to edit the Makefile to reflect the fact that "outelf.c" is gone and "outelf32.c" and "outelf64" are in. I (someone) should have run "mkdeps.pl" before the release. 0.99.01 should fix that - hpa took care of it - but there are other known problems... some of 'em fixed(?) and committed to CVS but not yet released. Only a couple hours old (fixed the /313 code and the /321->/324 codes... ???) Let 'em "mature" a bit... see if there's any immediate feedback from the development team... and if it looks good, we'll release 0.99.02 - still "for beta testing".

IF you need someone to host updated files, I can offer the services of
MicroCosmoTalk to present the source files (zipped or tarred packs).

Space to host files doesn't seem to be a problem. Besides SourceForge, any reasonably "stable" releases will wind up at kernel.org and probably a lot of other places... I don't think it's a "problem" that the "hot off the presses" files are only available immediately to developers - you might not *want* 'em. They're available by anonymous CVS within a day, if you do.

Besides the SF CVS repository, Nasm is being kept on something called "git"...

http://repo.or.cz/w/nasm.git

I need to get up to speed on "git"... We want to start using it instead of CVS (I'm not the only one who finds SF annoying, on occasion". It may be possible for "the public" to get "hotter" files from there (not currently... AFAIK... hmmm... I guess you *can*... click on "snapshot"...).

Thanks for the offer. You are, of course, welcome to host anything there you want - you've already got an improved Manual! (Thanks!) Another "mirror" can't do any harm. But I don't think it's a pressing need right now.

Best,
Frank
.

Relevant Pages

  • Re: Twelve Assembly Lessons
    ... You can download the 32-bit source code from CVS, it simply assembles ... with NASM. ... it is an extreme mess and as I have been ...
    (alt.lang.asm)
  • Re: How to update source for a driver
    ... L> I see updated source files for a driver that I would ... L> Is there a way to tell cvsup to just download new source for wi? ... L> across the board to just get the latest wi source files. ... L> I know I could download them all using the cvs web interface, ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Separete folders for form and source files
    ... >I am currently trying to get multiple overlapping projects (that share ... >source files) under revision control with CVS. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Separete folders for form and source files
    ... > I am currently trying to get multiple overlapping projects (that share ... > source files) under revision control with CVS. ... No, I don't think so, but plenty of people use RCS / CVS ...
    (comp.lang.pascal.delphi.misc)
  • Re: Confusing stack effects
    ... Nasm from CVS (the "macho" stuff is not yet released). ... Dunno. ...
    (alt.lang.asm)