On Wed, Jan 23, 2013 at 3:24 PM, Bruce Perens <[email protected]> wrote: > On 01/23/2013 11:51 AM, Albert Cahalan wrote:
>> but really it isn't good to be building all those libraries. > > You could probably split them each into its own separate package. But at the > moment I think we need to build them on Windows, and possibly MacOS. Tux Paint faces a similar problem. It requires SDL, SDL_image, SDL_ttf, SDL_Pango, SDL_mixer, libSVG and Cairo or libRSVG, and libpng. If they are missing, you're told what package you need to install. (by RPM name, but DEB and others could be listed as well) >> It is also unsafe. The wxWidgets installed on my system may have an >> incompatible ABI. This would cause crashes. > > There are definitely differences but in general it's that later versions of > wxWidgets have more facilities. I have started a port to an earlier version > of wxWidgets, but there's a lot of work to do and at the moment I'm out of > time. > >> Can something be done about this? > > If you're able to help, you're welcome to pitch in. I think so. Big changes may bring temporary turmoil, so I thought I'd better ask first. >> In case it would be useful, I can write a build system for fdmdv2 and/or >> codec2-dev as needed. > > We currently have autotools and I'd be happier with cmake, and I think from > the last time we discussed it that Dave Whitten is receptive to switching to > cmake. Obviously the build system should be an existing Open Source tool > with a good-sized community. I don't think it has to be that complicated, even when building libraries cross-platform. GNU make can do the job by itself. This makes builds way faster and shrinks the archive size. IMHO, automake and cmake and imake are all messy monsters. I'd use a modern non-recursive style, somewhat like the Linux kernel system but likely far smaller. The difficulty mainly comes down to decisions about Windows. Some projects choose Visual Studio. This simplifies the build situation, but exposes the project to compiler limitations. (and also is "not free", but if you cared you wouldn't use Windows) Some projects choose GNU make with the cl.exe compiler. Some projects choose msys or Cygwin for the compiler, building on Windows or building elsewhere. That is 6 options, not counting the fact that clang and icc can also be used. The choice with the lowest impact on the project is probably icc in Visual Studio, providing modern C while avoiding a unified Makefile. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
