Well thanks for the feedback. I've actually managed to find the answers to a few of these myself but uncover a couple of odd issues I'll bring up in another message.
That said, for the sake of the archive I'll answer some of my own questions:
1) I just wonder if anything in HLDS is needed to make the compile work.
Yes, You need tier0.so and vstdlib.so from the hlds/bin folder for the compile.
2) I'm aware theres some diff/patch files floating around to fix a lot of bugs in the SDK. Is there one for the current SDK and a "pure" HL2DM project?
BloodKenny told me no and that all his are posted on the wiki
3) How relevant is the known issues list on the Wiki for the current SDK build?
No definate answer, but I assume the ones marked as being relevant to the latest SDK are the most pertinent
4) We're using VS2005 for this, but I noticed that default Makefile points to the VS2003 vcproj file. Any issues/problems if I just make this point to the VS2005 one instead?
I managed to get vcpm to create a linux Makefile from the VS2005 project but when trying to compile I get G++ messages about no input files specified.
5) I dont seem to have libgcc_eh.a anywhere on my system - any idea what package it might be in?
Found it. If you are funning Fedora Core 6 like me and install the compat version of GCC 3.4.6. it puts the librarys in a different folder to /usr/lib or /usr/local/lib. I used locate to find it. - Jed _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
