Automake version 1.4 only lets you name your libraries with numbers, letters and underscores. They have changed this in version 1.6, but that one is pretty buggy still, and it still chokes when you try to create libnco_c++. That's bleeding edge technology for you. TODO 15 will have to wait.
rorik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm...yes, these autotools are very flexible so it's
a bit disconcerting when you run into a basic limitation
like this. The reason it matters is that I have a few
programs that link to libnco_c++. I know Unidata
builds with autotools and part of the netCDF
installation is libnetcdf_c++.a, but perhaps they
do not use automake and libtool and so they have
fewer limitations, but do not get the shared libraries,
which we definitely want. So, on your recommendation we will stay with libnco_cxx
for now, and I will change the old Makefiles
and my other programs to begin linking to that.
Thanks,
Charlie
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yep, Unidata does not use automake, they roll their own Makefile. If it is important, there is a fairly simple fix: We could edit src/nco_c++/Makefile.in and replace all occurances of xx with ++. Reprocessing Makefile.am with automake will change it back, however.
rorik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it's not important enough to justify a kludge which
cannot be fully automated and is foolproof.
we do not want to add
any more points of failure to the system.
so let's use libnco_cxx for linking until libnco_c++ is
fully supported by autotools. note that we will
leave the directory name, and include file as
nco_c++ and libnco_c++.h and we will change
the library back to that ASAP. does this sound good?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
15. Change libnco_cxx back to libnco_c++
Automake version 1.4 only lets you name your libraries with numbers, letters and underscores. They have changed this in version 1.6, but that one is pretty buggy still, and it still chokes when you try to create libnco_c++. That's bleeding edge technology for you. TODO 15 will have to wait.
rorik
Hmmm...yes, these autotools are very flexible so it's
a bit disconcerting when you run into a basic limitation
like this. The reason it matters is that I have a few
programs that link to libnco_c++. I know Unidata
builds with autotools and part of the netCDF
installation is libnetcdf_c++.a, but perhaps they
do not use automake and libtool and so they have
fewer limitations, but do not get the shared libraries,
which we definitely want. So, on your recommendation we will stay with libnco_cxx
for now, and I will change the old Makefiles
and my other programs to begin linking to that.
Thanks,
Charlie
yep, Unidata does not use automake, they roll their own Makefile. If it is important, there is a fairly simple fix: We could edit src/nco_c++/Makefile.in and replace all occurances of xx with ++. Reprocessing Makefile.am with automake will change it back, however.
rorik
it's not important enough to justify a kludge which
cannot be fully automated and is foolproof.
we do not want to add
any more points of failure to the system.
so let's use libnco_cxx for linking until libnco_c++ is
fully supported by autotools. note that we will
leave the directory name, and include file as
nco_c++ and libnco_c++.h and we will change
the library back to that ASAP. does this sound good?