bug-gift
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-GIFT] Major CVS checkin.


From: Wolfgang Müller
Subject: [bug-GIFT] Major CVS checkin.
Date: Thu, 3 Jan 2002 22:29:08 +0100

Hi,

Please test the new CVS checkin. So far it is tested only on my computer at 
home (SuSE 7.3). If noone complains about bugs within the next few days I 
will roll that CVS into release 0.1.7 (actually, there is already a 0.1.7 tag 
in CVS, but this was premature), and if 0.1.7 works nicely I'd like to call 
that 0.2 and anounce it on the gnu announcement list (any objections?).

What's new since 0.1.6pre3 are some minor stability fixes, fixing also the 
bugs mentioned on bug-gift and help-gift. However in terms of administration 
lots of things have happened:

- autoconf/automake generated files are no longer shipped with the cvs version
  use bootstrap-cvs.sh instead
- the make dist target works now (Yay! I'm starting to learn automake), this  
  is the precondition for more frequent and more reliable releases
- Includes are now written relative to the toplevel gift directory
  this simplifies installation.
- Include files are installed now. 
- the executable libMRML-config tells you about the linker flags
  needed to link your program to libMRML
- there is a plugin generator that creates an empty GIFT plugin with a given  
  name, ready for your extensions. It's currently undocumented, don't hesitate
  to ask the list and/or to contribute documentation.

However: gcc 3.0.1 as installed on my machine still makes trouble, as strings 
are unusable exactly the way Andreas described (sorry, it's an include in 
line 1, so I don't see anything that could be our, or in this case my, 
fault). Many projects seem to have this string-related problem. I have seen 
some package that recommends using >=3.0.2, I might try that out soon. If 
anyone does so before me, he/she is *very* welcome to tell this list if it 
works or not.

Cheers,
Wolfgang

PS: the above list of news will make it to the NEWS file with one of the next 
commits and the 0.1.7 release.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]