CoCoA » CoCoA-5

I believe the Linux kernel uses odd/even version numbers to distinguish between public releases and interim versions. Anyway, we could use such a simple technique (though it does require some discipline on our part).

I suppose the odd/even distinction should apply to the third number in the full version triple.

• It assumes the cvs copy in my "0.99/snapshot" directory is up-to-date.
• It copies packages and CoCoAManual directories into the MacCoCoA app directory (with the spurious CVS directories, a little tedious, but fixable)
• Makes a tgz of the MacCoCoA app directory (it seems that tgz preserves the icon... hard to believe)
• Prints the command line to send the tgz to the web site (does not send it automatically to prevent human errors..)

Problem for the GUI release:
even though it works reasonably well, there is a bug related to the fact that (by default) GMP is not thread-safe so the official GUI has to be linked to a GMP compiled with
--flag???
Does it have to be compiled or just linked?

This is an example showing the bug:
??????? (cannot find it, it's in my mail somewhere......)

Instructions:
The first time create a cvs "snapshot" directory:

  cd <my-dir>
  bash
  mkdir snapshot
  cd snapshot
  export CVSROOT=:ext:bigatti@www.dima.unige.it:/Volumes/Home_1/cocoa/cvs-repository
  cvs checkout CoCoALib-0.99

  cd CoCoALib-0.99
  ./configure <my-params>
  make -j3

  ~/shell-scripts/cocoa5-cvs-snapshot

The first time you also need to update the download web page.
(The following time the date is set automatically)

Prototype for gui on linux done.
Snapshot is online but still "server-invisible"

Now that I can compile cocoa on windows, I added some indications in script cocoa5-cvs-snapshot to help making the snapshot.

Fixed make-c5makefile.sh so that it deals with "-L" flag (John had fixed passing boost libs, but make-c5makefile.sh did not deal with the flag correctly)

I've been cleaning up my scripts and insterted them in CVS.
... as usual it is difficult to make things easy!
I have found the Mac command line to set an icon: now MacCoCoA.app dir is created from scratch automatically.

Currently fighting with making Emacs configuration easy.

I've been cleaning up my scripts and insterted them in CVS.
... as usual it is difficult to make things easy!
I have found the Mac command line to set an icon: now MacCoCoA.app dir is created from scratch automatically.

Currently fighting with making Emacs configuration easy.

Anna Maria Bigatti wrote:

works on mac and linux.
On linux also deals automatically with 32/64 bit binaries

simplifying the scripts (making a file with common functions and version number to be "source"d)
Hoping to make it work on windows too (but I need to install pdflatex on cygwin...)

Why do you need pdflatex on cygwin?

• make veryclean
• make dependencies
• make doc

Then make a tar-gz of the subtree, and use that to compile on other platforms. This way you should need txt2tags and pdflatex only on one "master" machine. There is a minor problem with make dependencies since we want the internal dependencies but not the external ones.

After speaking to Anna about my last comment, I have changed my mind.

She is the one who normally compiles releases, and prefers to work with sources obtained directly from the CVS archive; since CVS does not contain the "compiled" documentation, my proposed solution does not work.

It also occurred to me that should anyone wish to develop CoCoALib/CoCoA in a Cygwin environment then it is best for them if everything works correctly (assuming pdflatex can be found for cygwin).