I have a few find modules that I would be willing to contribute and I hope other people may find helpful (see http://crownandcutlass.svn.sourceforge.net/viewvc/crownandcutlass/trunk/Protocce/cmake/). The ogg and vorbis ones may need some tweaking since those libs don't have a default win32 path from an installer or anything. I'm not sure how to handle that. I'm also not very familiar with cmake yet, so I may be doing something incorrectly. Anyway, what is the preferred method for contributing modules? Add it to the "contributed macros" wiki page? Add a bug for each of them? Add it to the google group that was mentioned in this thread earlier? Just post it here? Let me know, thanks for the help.
David Thulson On Tue, Mar 4, 2008 at 8:51 AM, Mike Jackson <[EMAIL PROTECTED]> wrote: > Just my 2 cents on this subject: > I don't think the CMake community is large enough to support a > second site, yet. I would rather see all those little snippets of > information, code, examples and tutorials on the CMake Wiki or in the > CMake documentation itself. I think if there is more than one CMake > site at this present time that those new to CMake will find it > tougher to track down the information that they need. > > Also, what happens when you stop being a student with lots of time to > keep the site going? > > Then repository of CMake modules _is_ a good idea though. That > _could_ be put in the wiki if we really wanted it there. > > Again, just my 2 cents. > -- > Mike Jackson > > > > > On Mar 3, 2008, at 3:34 PM, Matt Williams wrote: > > > Hi everyone. > > > > I've got a proposal for you all which I've been thinking about for > > a while. > > Since cmake is now getting more and more widely spread, being used > > by people > > for both small, casual projects as well as monolithic projects > > (e.g. KDE) it > > seems like cmake itself, as well as the users of it could benefit > > from a > > community site of sorts. In my experience with opensource projects, > > one of > > the largest factors in how large a mindshare it has as well as how > > long it > > manages to hold on to that mind share is how strong a community it > > has. > > > > Now, this list is great; both for quick support as well as a direct > > line to > > the developers (kudos to Brad, Bill and co. for that) and the wiki > > is good > > for code snippets and extra documentation but I feel it could be > > better. > > > > I'm looking to see what you guys on this list think about me > > starting up > > a 'cmake community' site, possibly featuring the following: > > - News about releases > > - News about projects' success stories etc. > > - Simple beginner's tutorials > > - Tutorials about more specific tasks e.g. platform specific > > things (even > > when this isn't necessarily cmake specific) > > - A repository of Find*.cmake files including the ability to > > provide feedback > > to the module writer, such as improvements/patches > > - A repository of extra macros providing the same as the Find*.cmake > > repository > > - Discussion forums > > > > So, what do you guys think? Is this sort of site wanted/needed? Is > > this list > > and wiki enough and should our efforts be focused on them? I'd like > > to hear > > your thoughts before anything is set in motion. > > > > Finally, a little about myself: I've been using cmake ever since > > KDE first > > switched across to it (thankyou Alex) both for all my own projects > > as well as > > helping out a number of other projectsmore to a cmake system, > > particularly > > for its Linux and MacOS support. I'm a Physics University student > > by day and > > a KDE programmer by night. > > > > Regards, > > Matt Williams > > http://milliams.com > > > > > > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake > _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
