I mimicked imake in this case, and put an include to a file that uses variables for a cpp command. There might be a better way to do this (this might not even work at all), but I was hoping to stick to what works for now and autotoolize the code as we go along, the configure.ac also mimicks imake in the sense that it uses os detection rather than feature detection.
Thank you for your time, -Chase ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, October 23, 2019 4:45 PM, Jon Trulson <j...@radscan.com> wrote: > On 10/23/19 2:56 PM, Chase via cdesktopenv-devel wrote: > > > I tried to make these patches as distinct as possible, this constitutes > > an estimated 80% of the code covered > > Nice! I can see that took a long time. > > As discussed, I have applied these patches to the new > autotools-conversion branch. > > Nice work Chase - this gives us a good start on an autotools building > future :) > > I look forward to trying it out soon. > > How did you handle the cases where cpp is used to pre-process various > files (doc, .ksh scripts, UDB, etc)? I haven't looked yet. > > [...] > > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Jon Trulson > > "Nothing unreal exists." > -- Kiri-kin-tha > > cdesktopenv-devel mailing list > cdesktopenv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
