From: Wheeler, F. W (G. Research) <wh...@cr...> - 2008-09-24 22:49:12
|
Several files in contrib/brl/b3p/expat, under certain conditions, include expat_config.h, but it looks to me like expat_config.h does not exist in VXL. This is causing errors on my dashboard FreeBSD builds, which are on machines that do not have a native expat, and thus try to build and use the implementation in brl/b3p/expat. Since brl/b3p/expat is an implementation of expat it seems it should be self-contained and not rely on an expat_config.h from elsewhere. Is this a bug? Am I misunderstanding something? Thanks, Fred |
From: Matt L. <mat...@gm...> - 2008-09-25 13:35:13
|
Fred, I'll talk to some people here and try to figure the expat issue out. I have seen this error before and I thought someone had fixed it. Apparently not. If I remember correctly, that expat_config.h file is generated on Linux systems during the expat install and contains system specific parameters. We can not just upload a static copy. This file is not used on Windows (most Brown developers use Windows) and has not given me trouble because I happened to have expat installed independently on my Linux machines. I think we will probably need to make CMake generate this file when needed. --Matt On Wed, Sep 24, 2008 at 6:48 PM, Wheeler, Frederick W (GE, Research) <wh...@cr...> wrote: > > Several files in contrib/brl/b3p/expat, under certain conditions, > include expat_config.h, but it looks to me like expat_config.h does not > exist in VXL. This is causing errors on my dashboard FreeBSD builds, > which are on machines that do not have a native expat, and thus try to > build and use the implementation in brl/b3p/expat. Since brl/b3p/expat > is an implementation of expat it seems it should be self-contained and > not rely on an expat_config.h from elsewhere. Is this a bug? Am I > misunderstanding something? > > Thanks, > Fred > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Vxl-maintainers mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > |
From: Bill H. <bil...@ki...> - 2008-09-25 16:43:22
|
Matt Leotta wrote: > Fred, > > I'll talk to some people here and try to figure the expat issue out. > I have seen this error before and I thought someone had fixed it. > Apparently not. If I remember correctly, that expat_config.h file is > generated on Linux systems during the expat install and contains > system specific parameters. We can not just upload a static copy. > This file is not used on Windows (most Brown developers use Windows) > and has not given me trouble because I happened to have expat > installed independently on my Linux machines. I think we will > probably need to make CMake generate this file when needed. > You might want to just copy the cmexpat directory out of cmake. It is all cmake'ified and builds on all the platforms that cmake builds on. -Bill |
From: Matt L. <mat...@gm...> - 2008-09-25 16:00:30
|
Bill, Thanks! I didn't realize that CMake had expat built in. We might just have to take you up on that offer. I think the easiest way to resolve this is to copy cmexpat. --Matt On Thu, Sep 25, 2008 at 11:50 AM, Bill Hoffman <bil...@ki...> wrote: > Matt Leotta wrote: >> >> Fred, >> >> I'll talk to some people here and try to figure the expat issue out. >> I have seen this error before and I thought someone had fixed it. >> Apparently not. If I remember correctly, that expat_config.h file is >> generated on Linux systems during the expat install and contains >> system specific parameters. We can not just upload a static copy. >> This file is not used on Windows (most Brown developers use Windows) >> and has not given me trouble because I happened to have expat >> installed independently on my Linux machines. I think we will >> probably need to make CMake generate this file when needed. >> > > You might want to just copy the cmexpat directory out of cmake. It is all > cmake'ified and builds on all the platforms that cmake builds on. > > -Bill > |