> > but unless I'm being really stupid about something, there is no easy
> > DOCUMENTED way to set things like the compiler and cflags in one place,
> > and editing _24_ Imakefile_s is not really something I want to do.
> > Am I missing something obvious?!?
>
> Configuring the compiler and flags is supposed to part of the imake
> configuration on your system, not part of fvwm. In fact, that is the
> whole point of the imake scheme, that the application does *not* need to
Right.. my problem is that whoever set things up on my system
should be executed for being a moron. I still think that my point was
valid, however, because some of the modules were compiled with CFLAGS,
some with CDEBUGFLAGS, some had FVWMLIBS included, some only included
LIBS, and so on..
At any rate, I took 2.0.41 home and compiled it under Ultrix
and it worked PERFECTLY. Much improved from older versions-- I had to
change two lines (paths to xpm stuff) and then the rest was automatic.
One small problem I did notice with the fvwm_convert script in
the utils directory: under Ultrix, it needed to run /bin/sh5, and there
is no /dev/stderr, so I changed those lines to /dev/console. I think it
might be nice to stick some comments in the header of the script to that
effect.
And finally, I've gone through the sample .fvwm2rc file, changed
it to my liking, reorganized all of the various options into sections,
and commented almost everything. This is for friends who can't be bothered
to read documentation, but it might be a useful replacement for the
system.fvwmrc. Shall I send it to the list or upload it somewhere?
-Eli
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Apr 12 1996 - 08:51:47 BST