On 07.02.2010 16:29, Mike Gist wrote: > On the subject of SDK binaries again; I'm happy to make the windows ones. > Is there any preferred method of packaging them? We want them > shared-libs non-static? > What should the SDK contain? All CS apps?
See http://www.crystalspace3d.org/trac/CS/wiki/PackagingIdeas for some ideas. There's also already some stuff (scripts to generate MSIs) in scripts/msi/. Even if you frown upon MSIs for distribution take a look at what packages this would currently generate. I don't think the division was too bad ;) Furthermore, check out the "file list" stuff, as that should help splitting up the CS data/files into separate distinct groups (such as "runtime data" which is likely needed by about every client app and "demo data" which is only needed by CS demos) instead of having mumble-jumble of everything (which the CS source tree is). So even if you end up saying "I just rather zip everything up" these file list can give you _what_ should go into a specific zip. And wrt binary creation: I think it's good to aim for having some scripts for easy-as-pie binary SDK generation. Less complicated means more likely it's done; also, it helps with splitting the load (eg not one person having to build all SDKs, but one can take MSVC 8, one MSVC 9, yet another MinGW and so on). -f.r. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[email protected]?subject=unsubscribe
