Well combining the projects would take longer to link, yes. It would
take longer to compile the first time, yes. It would take longer to get
by CVS, yes.
But after that first compile, it would take as long as before (except
for link, which would take maybe 3-5 more seconds when
Xiph's code is portable to all platforms. A DLL isn't. That's my main
Remove the use of separate DLLs. One app.
Ability to change Xiph's code if we need to. No need for a specific
version of the DLL.
Closely follows Open Source doctrine by providing source code with the
executable, instead of a nice link saying "you can get the source for
this at this address".
Way to implement it in VC:
Add it as a separate project, with our software dependent of that other
If you don't add the source, I will have to anyways in the Mac version.
There are no precompiled version for Mac. So we'd have all the
inconveniences and no benefit from your proposal.
On Saturday, Dec 14, 2002, at 13:59 America/Montreal, Glenn Maynard
> On Sat, Dec 14, 2002 at 10:13:52AM -0500, Michel Donais wrote:
>> Mmmm, I'm wondering if there is a way to link our project to the xiph
>> CVS, to download the source code directly when we get the l8test
>> version on our side... maybe with GNU make.
>> ... or simply adding the two projects to our CVS.
>> Adding the different DLLs isn't the best idea. For the Mac version I
>> would need to recompile for Mac, as there are no framework module for
>> Ogg / Vorbis (none I know of, anyways). And it would duplicate code as
>> compiled / source, possibly to the point where we'd have some minute
>> differences between two versions, potentially causing random bugs in
>> one of the platforms.
> Two projects? We use about 14 libraries.
> Combining the projects would be a hassle and make the SM project huge,
> make linking take even longer (since it'd be linking in all of that
> code instead of just importing references), and make updating them
> Requiring people to compile them all in VC as separate projects would
> a huge pain, since they'd have to be opened and compiled individually.
> This isn't a big deal in *nix; we can do it with a makefile (and for
> ones that aren't modified, people can use existing installs).
> Glenn Maynard
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> Stepmania-devs mailing list