On 7 June 2010 15:14, Kai Tietz <[email protected]> wrote: > 2010/6/7 Ozkan Sezer <[email protected]>: >> On Mon, Jun 7, 2010 at 12:37 PM, Kai Tietz <[email protected]> wrote: >>> 2010/6/7 Ozkan Sezer <[email protected]>: >>>>>> >>>>> >>>>> Well, the only solution I see here for the ddk-optional SDK is, that >>>>> we do a fork of it and have to maintain it by ourself. The only need >>>>> we would have here is a volunteer doing the manual merge and which >>>>> signs responsible to build up an testsuite for it. >>>>> We should keep in experimental branch the link to reactos-svn, but >>>>> replace the links in branches. When we found a volunteer for it, we >>>>> can proceed on this. >>>>> >>>>> Kai >>>> >>>> What I do for direct-x, I can do for ddk, too. >>>> >>>> -- >>>> Ozkan >>>> >>> >>> Well, if you commit for this task, I am fine. Major thing here is, >>> don't load too much burden on your shoulders. >>> >>> Kai >>> >>> -- >>> | (\_/) This is Bunny. Copy and paste >>> | (='.'=) Bunny into your signature to help >>> | (")_(") him gain world domination >>> >> >> OK, I created a "ddk_test" directory under >> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/ >> ... with an updated README.ddk file included. >> If this is OK, the reactos svn-links should be nuked and the whole >> contents of mingw-w64-headers/ddk/ directories under both the trunk >> and the v1.0 branch should be replaced by the contents of this new >> experimental/ddk_test directory. >> >> As of yet, I put together all things necessary as the first step. >> There should not be any missing dependencies. However, there may be >> missing headers, so have a look at the reactos repo at >> http://svn.reactos.org/svn/reactos/trunk/reactos/include/ (or >> svn://svn.reactos.org/reactos/trunk/reactos/include/) and see if >> there are more ddk headers that needs to be here. >> >> I also did not take any action with the POINTER_64 problem in >> ddk/ntdef.h (reported by Henry Nestler), yet. Kai: what would be the >> best for it? An empty #define for POINTER_64?? >> >> -- >> Ozkan >> > > Ozkan, > > thanks for the initial step. Please contact AmineKhaldi (he is on irc) > from ros. He wants to support us for missing headers and > synchronization issues. > > Cheers, > Kai >
How is it going to be done? Cause e.g. using bzr I have locally merged reactos svn include dir with mingw-w64 both trunk & 1.0 branches. From these you can merge from both svn repos and dump into svn =) The benefit is that you will need to do renames just once and each time we will do bzr merge from reactos we just will get conflicts on things that we have modified locally and we can shuffle all files around however we like ;-) After the first subdir merge (i've subdir merged just the ddk/ headers and not the whole include dir) that I've done it's simple as $ bzr merge svn://reactos/path/to/headers $ bzr push svn://mingw-w64 Cause we still want something we can merge automatically & daily to do nightly builds. (the whole reacos svn repo is getting imported every 6 hours into bzr branch on launchpad same as mingw-w64, gcc & binutils) ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
