I am new to cppUnit and to Linux but I want to learn both (maybe that's my problem)...anyway...so I'm not familiar with the Linux tools.
I've just pulled the cppUnit code from the cvs repository then executed the 'autogen.sh' shellscript as is mentioned in a file somewhere (I forget at the moment). The next instructions I can find (found in a different file) say to execute the .configure script...but there isn't one.
I've figured out that I can issue autoconf and that generated a ./configure...so then I execute that. It does some stuff then exits. The next step I can find says to execute 'make'..well there is no makefile or Makefile..just something called Makefile.in.
I've figured out that there is an automake command. I execute that, which delays briefly then returns...still no makefile though, I dunno what it did.
Why is it sooooo hard to find ANY information on how to compile the stupid thing??? What is sooo hard about
"To build the cppUnit framework...
step 1)
step 2)
step x)
congradulations you are now ready to build and test more reliable code"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, and how would I build this thing if I didnt' have access to these tools (autoconf, automake, etc)???
My ultimate goal is to try to use this thing on a proect at work, on a machine running SunOS 5.9 and for which I do not have administrative privelages, and odds of getting an administrator to install stuff is ... well lets just say I have a better chance of hitting the lottery.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can install the autotools in your home directory. I used to do that when building on sf compile farm.
Another option is to either use a released version of cppunit (you don't need the autotool to build it) or generate a distrib tarball using:
make distcheck
Baptiste. -- CppUnit maintainer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The build instruction you found in README.CVS are accurate.
I finally just managed to get my linux vm back and was just as stunned as you: where the hell is configure ?
It seems that the message printed by automake is an error (even if it doesn't say so), and the autogen process is aborted.
I've tracked the issue down to a patch submitted to fix aclocal warning. To get a correct build, retrieve revision 1.2 of config/bb_enable_doxygen.m4:
cvs up -r 1.2 config/bb_enable_doxygen.m4
Notes that you would make your life easier if you used the stable version of cppunit as it is known to build correctly. Issues are to be expected when using cvs version, specifically on the unix side since I have a windows box.
Baptiste. -- CppUnit maintainer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am new to cppUnit and to Linux but I want to learn both (maybe that's my problem)...anyway...so I'm not familiar with the Linux tools.
I've just pulled the cppUnit code from the cvs repository then executed the 'autogen.sh' shellscript as is mentioned in a file somewhere (I forget at the moment). The next instructions I can find (found in a different file) say to execute the .configure script...but there isn't one.
I've figured out that I can issue autoconf and that generated a ./configure...so then I execute that. It does some stuff then exits. The next step I can find says to execute 'make'..well there is no makefile or Makefile..just something called Makefile.in.
I've figured out that there is an automake command. I execute that, which delays briefly then returns...still no makefile though, I dunno what it did.
Why is it sooooo hard to find ANY information on how to compile the stupid thing??? What is sooo hard about
"To build the cppUnit framework...
step 1)
step 2)
step x)
congradulations you are now ready to build and test more reliable code"
Forgot to mention...
Linux: Fedora Core 3.x with all current updates.
Oh, and how would I build this thing if I didnt' have access to these tools (autoconf, automake, etc)???
My ultimate goal is to try to use this thing on a proect at work, on a machine running SunOS 5.9 and for which I do not have administrative privelages, and odds of getting an administrator to install stuff is ... well lets just say I have a better chance of hitting the lottery.
You can install the autotools in your home directory. I used to do that when building on sf compile farm.
Another option is to either use a released version of cppunit (you don't need the autotool to build it) or generate a distrib tarball using:
make distcheck
Baptiste. -- CppUnit maintainer.
The build instruction you found in README.CVS are accurate.
I finally just managed to get my linux vm back and was just as stunned as you: where the hell is configure ?
It seems that the message printed by automake is an error (even if it doesn't say so), and the autogen process is aborted.
I've tracked the issue down to a patch submitted to fix aclocal warning. To get a correct build, retrieve revision 1.2 of config/bb_enable_doxygen.m4:
cvs up -r 1.2 config/bb_enable_doxygen.m4
Notes that you would make your life easier if you used the stable version of cppunit as it is known to build correctly. Issues are to be expected when using cvs version, specifically on the unix side since I have a windows box.
Baptiste. -- CppUnit maintainer