Let's back up a little.
*Goal*: someone can go to the BOINC web site,
click on "Built the BOINC client",
and get cookbook for the platform and IDE of their choice.
("cookbook" means a complete list of instructions,
no figuring out anything required).
*Non-goal*: someone can explore the BOINC source tree
and figure out how to build the client.
To achieve the goal, we need to fix the Wiki pages.
The location of project files doesn't matter; let's leave them where they are.
There have been lots of well-meaning but misguided changes to the wiki pages.
We need to undo them.
-- David
On 11/30/2015 7:36 PM, Charlie Fenton wrote:
On Nov 30, 2015, at 7:24 PM, Rom Walton <[email protected]> wrote:
Just for clarification purposes, changes to the project files around is not the
same thing as changes to the source files. It doesn't really become a major
headache until somebody starts to refactor the source files.
Changes to the directory tree structure require changes in the Xcode project
file and build scripts, not to the *.c and *.cpp files. However, it can
complicate porting of *.c and *.cpp files to a branch with a different tree
structure.
Cheers,
--Charlie
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
