[Tdg] Code commit

[Alex Norman]

So I've taken a look at the code in the repo, I've started making a Makefile but
I really think we should reorganize the code.

right now we have:
core/branches/mint/source/{core, audio_system, ...}

I think it should be more like

core/{branches/, trunk}
core_easy/{branches, trunk}
audio_system/{branches, trunk}
documents
etc.

basically, each system, while they require the core, is an independent project,
and should be separated as such. [have their own makefiles, etc] early in this
project we talked about this, we don't want to require all the libraries, well,
we shouldn't build our project up like that either.

Also, what's with all the folders in core?
I assume the platform dependent stuff might go in a "platform" folder, but most
folders simply have 2 files, a header and an implementation file, it is pain, It
makes more sense to me to have all of these implementation files in a "source"
dir [possibly excluding the platform dependent stuff], and all of the headers in
a "include" dir.. or hell, put them all together... that would make life of
makefiles easier, and, the core shouldn't be that big, so managing 1 "source"
directory won't be a problem.

so I propose we do this:
svn/core/branches/source/[all the cpp files for core]
svn/core/branches/include/[all the header files for core]

-Alex

On  0, Graham Wakefield <wakefield at mat.ucsb.edu> wrote:
> Aha, needed a main function in mac_main.cpp, that's all.  Now it  
> builds AND runs.  So fancy!  So committed!
> 
> G
> 
> On Mar 2, 2007, at 9:29 PM, Graham Wakefield wrote:
> 
> >OK here's my report on trying to build libmint.a (core)
> >
> >stdint.h and inttypes.h are M$ specific so it shouldnt' be in the / 
> >includes folder, they should be in a M$ specific folder.
> >
> >mfile.cpp is windows stuff too, right?  "file.h" and "debug.h" fail  
> >on that.
> >
> >Otherwise, compiling all of /core (except the non-carbon platform  
> >events) works.
> >
> >Is there a way to take #define MINT_WINGL out of the main.cpp?   
> >Like, can you put it in the project solution as a build flag?  You  
> >can in Xcode (I have done so for BUILD_MACGL).
> >
> >A general comment, the header #ifndefs are a bit generic (e.g.  
> >EVENT_H, DEF_SYSTEM etc), I think they should be more specific to  
> >avoid clashes, e.g. INC_MINT_EVENT_H, INC_MINT_SYSTEM_H.
> >
> >I couldn't build the test app because of an error 'Event has not  
> >been declared' in msystem.h & graphics_system.h.  When I changed  
> >EVENT_H to INC_MINT_EVENT_H, it built perfectly.  I've changed the  
> >#ifdefs throughout the source to reflect this.
> >
> >Of course, building is one thing.  It doesn't run (EXC_BAD_ACCESS)  
> >but whatever.  I've committed the changes.
> >
> >G
> >
> >
> >On Mar 2, 2007, at 8:00 PM, Rama Hoetzlein wrote:
> >
> >>I posted the library list to the wiki:
> >> http://tdg.mat.ucsb.edu/index.php/Library_Build_List
> >>
> >>So far only core, core_easy and graphics are ready for build. If  
> >>you guys want to use other names for libs like _lnx_ or _leenux_,  
> >>_mc_, or  _mwac_ please feel free.
> >>
> >>rama
> >>
> >>
> >>Graham Wakefield wrote:
> >>
> >>>Hi Rama,
> >>>
> >>>I'm making the Xcode project now.
> >>>
> >>>Remind me - what are the different solution names (and libraries  
> >>>that  they produce)?
> >>>
> >>>Thanks
> >>>
> >>
> >>_______________________________________________
> >>Tdg mailing list
> >>Tdg at mat.ucsb.edu
> >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> >
> >_______________________________________________
> >Tdg mailing list
> >Tdg at mat.ucsb.edu
> >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg
> 
> _______________________________________________
> Tdg mailing list
> Tdg at mat.ucsb.edu
> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg