(06-18-2009, 03:25 AM)Xtreme2damax Wrote: [ -> ]I still believe that all threads for builds by non-developers should be merged centrally in the Unofficial Builds by non-devs, and the thread restickied.
This should reduce the clutter, and ensure that the Unofficial Builds by non-devs thread is updated more frequently than it formerly was. There's no reason to have a ton of separate threads for builds by non-developers, the only builds that should have separate threads is the Un(official) Bi-Weekly builds of Dolphin and specialized builds of Dolphin where new features or fixes have been added by coders before they are committed to the svn repository.
but that like... needs some1 who wants to update that stuff >_>
(which wont be me!)
i'd be willing to update it
Why can't we just have a script that builds the latest SVN every hour or so? Then cache the latest 20, so you can choose what you want. All these unofficial builds are fail.
(06-18-2009, 05:24 AM)gcp111 Wrote: [ -> ]Why can't we just have a script that builds the latest SVN every hour or so?
that's like the same idea that gabest used for Gsdx
(06-18-2009, 05:26 AM)LuisR14 Wrote: [ -> ]that's like the same idea that gabest used for Gsdx
Then why don't we do it...
Pretty easy to implement I guess.
(06-18-2009, 05:24 AM)gcp111 Wrote: [ -> ]Why can't we just have a script that builds the latest SVN every hour or so? Then cache the latest 20, so you can choose what you want. All these unofficial builds are fail.
every hour is fail like shitting brix
every day or half a day is better
EDIT: and while you are at it, why not make a script that checks svn and compiles if new commit was done
(06-18-2009, 05:32 AM)Daco Wrote: [ -> ]EDIT: and while you are at it, why not make a script that checks svn and compiles if new commit was done
I'd love to, but no. And I have no clue how to communicate with SVN (is there a libsubversion? Or just poll the server and kill it
)
This thread is frequently updated, it will always be on top, so why do you need a sticky?