On 10/22/12 02:49, Jon Trulson wrote:
> Actually, I'm thinking maybe we use an autoconf (configure) run as
> part of the make includes phase.  It's sole job would be to detect
> various things about the system (like availablility of va_copy, tirpc,
> sys_errlist/errno, installed locales, etc) and create a
> cdehostconfig.h file (and maybe a makefile that could be included in
> other makefiles).
>
> I am not proposing converting to autoconf completely, but rather
> having one run as part of the make includes phase (in config/) that
> could determine stuff like this at build time.  I did this for an
> imake based project once before (NAS) and it worked well for figuring
> out stuff like this.
>
> Could solve a lot of these types of problems...
>
Sounds like a great plan. This certainly gets my vote.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to