Suggestions for the VS2010 project structure

26 views
Skip to first unread message

EdwardP

unread,
Sep 7, 2012, 11:28:20 AM9/7/12
to G3D Users
Chaps,

I'd like to suggest a small change for consideration. The current
VS2010 sub-projects all reference their include files based on the
$SolutionDir path. If this could be changed to $ProjectDir
(particularly in the G3D & GLG3D) it would mean that they could more
easily be added to other, new, solutions. When debugging I find it
really useful to add a the G3D/GLG3D projects to my own solution to
help me work my way around the code during development. I don't think
the change above will have any impact in your own build environment
because the project and solution for G3D are co-located - but it would
simplify their addition to other solutions.

Just a thought.

E

PS I also noticed that G3D explicitly adds the includes to GLG3D in
the project - given their intended relationship, I suspect that this
isn't intentional and I haven't found any problems in removing it?

EdwardP

unread,
Sep 7, 2012, 11:35:10 AM9/7/12
to G3D Users
Oh, and I forgot. Build Events command line path to copyifnewer would
need the same change.

Cheers

E

Morgan McGuire

unread,
Sep 7, 2012, 11:37:10 AM9/7/12
to g3d-...@googlegroups.com
That's a good idea.

Prof. Morgan McGuire
Computer Science Department
Williams College
http://cs.williams.edu/~morgan

EdwardP

unread,
Sep 10, 2012, 5:36:34 AM9/10/12
to G3D Users
I'm afraid my 'PS' above was wrong - ImageFormat.cpp in G3D *does*
have a dependency on "GLG3D/glheaders.h" so I don't think G3D can be
built independently at the moment. I hadn't forced rebuild after my
change - sorry.

E

Morgan McGuire

unread,
Sep 10, 2012, 8:34:22 AM9/10/12
to g3d-...@googlegroups.com
It can. E used independently but not built indepe dentlt

Sent from my phone
Reply all
Reply to author
Forward
0 new messages