Jan Kiszka wrote:
Paolo Mantegazza wrote:
Jan Kiszka wrote:
Paolo Mantegazza wrote:
...
I think your problem should be solved by "vulcano". It is there I'll
put your fixes too.
Not yet, vulcano's configure.in this awaits some versioning fix in
AC_INIT().
Cna you explain it please. I do not understand your comment.
Paolo.
Index: configure.in
===================================================================
RCS file: /cvs/rtai/vulcano/configure.in,v
retrieving revision 1.3
diff -u -p -r1.3 configure.in
--- configure.in 18 Mar 2005 09:29:58 -0000 1.3
+++ configure.in 22 Mar 2005 10:12:09 -0000
@@ -1,11 +1,11 @@
dnl Process this file with autoconf to produce a configure script.
AC_PREREQ(2.59)
-AC_INIT(rtai,magma,[EMAIL PROTECTED])
+AC_INIT(rtai,3.2,[EMAIL PROTECTED])
Actually, should be something like
+AC_INIT(rtai,3.2-test3,[EMAIL PROTECTED])
CONFIG_RTAI_VERSION_MAJOR=3
-CONFIG_RTAI_VERSION_MINOR=1
-CONFIG_RTAI_REVISION_LEVEL=90
+CONFIG_RTAI_VERSION_MINOR=2
+CONFIG_RTAI_REVISION_LEVEL=0
2.0 is likely better for the final 3.2 release. Keeping 3.1.9xx for the
-test series would keep the consistency regarding increasing version stamps.
AC_CONFIG_HEADERS(rtai_config.h)
AC_CONFIG_AUX_DIR(base/config/autoconf)
That's how we can then process the version reliably using scripts (i.e.
RTnet's configure).
Jan
_______________________________________________
Rtai-dev mailing list
[EMAIL PROTECTED]
https://mail.gna.org/listinfo/rtai-dev
--
Philippe.
