Game Development Community

Doc dir?

by asmaloney (Andy) · in Torque Game Engine · 09/29/2006 (4:43 pm) · 5 replies

Sorry if this is covered somewhere... couldn't find a solution. It might be a Mac-specific thing so I thought I'd post here...

I've downloaded the file TorqueGameEngineSDK-1-4u.tgz. I decided to build a local copy of the code ref using doxygen, but found that the docs dir does not exist. This is supposed to have the doxygen config file [doxygen.html.cfg] in it...

Where do I get this file? [Please don't say I have to get the whole CVS for this file...]

Thanks!

#1
10/02/2006 (8:55 am)
[How am I going to get a reply... Oh! I know!]

blah blah C4 blah blah blah LawMaker blah blah TAT is a terrible name blah blah blah

Anyone?
#2
10/02/2006 (11:23 am)
Worst case, you can create your own Doxygen config file. It's not that hard -- and you get to customize the output to your liking!

Btw: the documentation for C4 is no better than the documentation for TGE. They both are pretty incomplete, and lack good overview and cookbook sections.
#3
10/02/2006 (11:45 am)
Oh no!! I didn't want to start another C4/LawMaker thread - I was joking because they seem to be getting a lot of attention...

Thanks for the response. I do know how to use doxygen, but I was following the instructions [How to Regenerate the Torque Engine Reference] for building the docs and it doesn't work [on the Mac - maybe it does on Windows]. Other people are going to run into it, so it should be fixed.

I figured it was just a packaging issue - they were forgotten in the Mac package or something.
#4
10/02/2006 (2:59 pm)
Quote:Other people are going to run into it, so it should be fixed.

So far, my experience has been that "other people will run into it" isn't enough to make GG fix it. They seem to rely pretty heavily on community development and patches...
#5
10/02/2006 (4:12 pm)
This is unfortunate and disappointing because then everyone has to spin their wheels to solve the same problems over and over again. Using the forums and resources is not exactly the 'support' I was expecting, but I guess I can rationalize it by saying I paid $100 for some source code.

If they're going to rely on the community, then they should at least provide a better structure for patches and resources...