Hello, Per previous RFC, I've splitted and migrated CeGCC SVN codebase to Git. For each upstream project, there is a separate git repository. Potentially, that will allow to rebase CeGCC patchset onto pristine upstream tree and follow upstream development more easily and/or maintain CeGCC patchset in better form.
At this time, only w32api tree was rebased against upstream. w32api also acquired lot of patches, thank to which it's now possibly to compile number of 3rd-party applications, like GSPlayer, FtpSvr, tMan, Win32++, etc. The fact that there're number of repositories now doesn't mean that now it is harder to build entire toolchain - there's a meta-repository, cegcc-build, provided, which uses git submodules to pull all needed bits easily. Actually, I structured this build repository along the lines of http://en.wikipedia.org/wiki/Convention_over_configuration - you just need to clone that repository, follow very simple instructions in README (nothing to edit or configure manually), and get the toolchain built by running one command (which is itself just old good build-mingw32ce.sh). Repositories are currently hosted at Gitorious - I'd like to discuss that further, ideally I'd like to see them hosted within bounds of existing CeGCC project, at SF.net. I'd appreciate if all interested parties tried it, comments are welcome. http://gitorious.org/cegcc Quick start: git clone git://gitorious.org/cegcc/cegcc-build.git Then follow instructions in cegcc-build/README (http://gitorious.org/cegcc/cegcc-build/blobs/master/README) -- Best regards, Paul mailto:pmis...@gmail.com ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
