On Fri, 3 May 2002, Kenneth J.Davis wrote:
> Dom Lachowicz <[EMAIL PROTECTED]> wrote on 5/3/2002 2:10:47 PM: > > > >On Fri, 2002-05-03 at 14:01, Kenneth J.Davis wrote: > >> So popt is now required on all platforms? (ap Args seems to require it) > >> I am just asking so I can see about fixing the Windows build in the proper > >> manner (either making popt included, or making sure it is not used), although > >> I'd be more than happy if someone else commits a fix before I get a chance to. >:-) > > > >POPT is now required on all platforms so that we have some sane > >command-line processing and equal features across all platforms, where > >applicable (win32 might have a hard time implementing --print, for > >example). > > > >The best way to fix this is to extend AP Win32App from AP App and follow > >the code used in the ap UnixApp::main. > > > >Dom > > Thanks, > I will see about doing this tonight/tommorrow unless someone is already > planning on doing it (or has already started on/done it). > > Jeremy Davis > [EMAIL PROTECTED] > > Jeremy - I've been looking into this. popt is there and can be including in the Win32 required, but there is a problem. popt seems to require libintl which as far as I know isn't included currently as a peer library. I have a Win32 version of it and will pay around with it. If popt has to be required for "sane-ness" then I suppose that libintl will too. To me, the popt lib doesn't provide a "sane" system but makes all systems work like *nix where --foo=bar and other things are used. I have not found the /foo=bar would work which is the expexted for Win32 users. Perhaps I need to dig more. Cheers! Michael D. Pritchett
