Upper or lower case modfile name solution

[frae]

The current way to determine whether generated mod files have upper or lower case is not working for all compilers, e.g. the efc fails. I have implemented a quick and dirty solution directly into the configure files, thus I can start the testing. They are in revision 665, and allow to pass variables MOD_NAMES_UPCASE or MOD_NAMES_LOWCASE to the configure script. configure just does a test if one of the 2 is set and overwrites anything coming from the previous test. The solution might be overwritten with an update to configure but at least I can do some more testing ;-)

The solution looks like this:

# overwrite mod name convention, quick and dirty
# and should really be in configure.ac. Does the
# job for efc compiler.
if test -n "$MOD_NAMES_UPCASE"; then
  echo 'Found user set upper case module file.'
  CM_FC_UC_MODNAMES=yes
else
  if test -n "$MOD_NAMES_LOWCASE"; then
     echo 'Found user set lower case module file.'
     CM_FC_UC_MODNAMES=no
  fi
fi

[marq]

With changeset [694], configure gets two new command line arguments, --with-uppercase-modnames and --with-lowercase-modnames. These can be used to overwrite the default settings when configure is run. Together with the improvements in the compiler detection, this should suffice for most cases (although it still isn't an automated version). So I leave this open for the time being...

[marq]

I have not heard anything against this solution for more than half a year, so I consider the problem fixed with the solution implemented in r694.

[(none)]

Milestone 0.9 deleted