Is 1.4 out?

#1 Update: Now it is

#2 Anyone know if it compiles under GCC4 yet?

#3 I tried, and got an error, never looked into it.

Edit: Says no rule to make target out.GCC3.Debug/console/gram.obj

Got off the CVS Yesterday

#4 The only compilers that work right now are the Visual Studio series, excluding version 6 (and below of course).

#5 @Chris, that means you need to add console/gram.h to your targets.torque.mk file under engine I believe.

I sure wish I understood templates, vectors and STL better,since thats where my compiles keep aborting at. Something about console being defined without a type.

Unfortunately my C++ skillz are pretty rudimentary for some reason even though I've been working with it since the early 90s, I guess I'm just having a hard time learning it.

On a sidenote, all us Linux and maybe even Mac and TBE folks should knock our heads together, and try to get each and everysingle issue solved from the CVS build, maybe start a thread about it or something.

Word from Ben last I checked was that GG doesn't actually maintain the Linux ports anymore, and it's more or less a community thing at the moment. I hope that was sarcasm or I mis-read what he was saying, since my whole reason for choosing GG in the firstplace was crossplatform comptability, and the fact that I only run Linux, if at all possible. Well that and the community of course ;)

#6 @Dreamer:

We have people do it out of house, ie, currently Ron Yacketta is the lead guy on that. We like Linux and we are happy to enable support for it but there's just not much of a game or tools presence on it, so it's hard for us to dedicate a lot of resources to the task (like a full time Linux guy). Most software for Linux is developed through community members stepping up to the plate, so we figure that it's appropriate for Torque to work the same way. :)

Also, bear in mind that Ron, Paul, and I have done a tremendous amount of work on our respective platforms since the last CVS drop. Once we get the installers finalized, we'll also mirror the changes into CVS. These include fixes for MOST of the issues out here on the forum. We just don't want to take the time and focus off of getting the final release done.

#7 Ok, then I completely misread you and I'm sorry about that. In another thread you said something to the effect of there are no "these guys", and Linux support was more or less a community thing. Which I understood to mean, that GG wasn't going to support Linux and/or we would have to port everything ourselves.
Eitherway I'm glad to know you don't intend to drop support for Linux, it's my main reason for being so gung-ho for GG ;)

#8 I can say that with some difficulty (happy to help!), GCC 4 works on the Mac build presently.
You certainly have to read the README file in the pb folder. Once again, happy to help others succeed to at least the extent I'm presently enjoying.

tone

#9 I tried to get the GCC variant running.

The good news: it compiles. The bad news: the linker is missing some files.

The makefile seems very much out of date. Maybe this is helpful to someone.

I checked out HEAD and did the following (win32):

1.

Change in /torque/mk/conf.GCC3.WIN32.mk
  MKDIR=mkdir $(@:/=)
in 
  MKDIR=mkdir -p $(@:/=)

(thanks, John Kabus)

2. add the vorbis folder from 1.3 into the 'lib' folder

3. in engine/targets.torque.mk change these lines

console/gram.cc \
  console/scan.cc \
to
  console/basgram.cc \
  console/basscan.cc \

Also comment out:
  # dgl/rectClipper.cc \
  # gui/controls/guiOtherTreeViewCtrl.cc \

4. in engine/core/torqueConfig.h comment out

// #define TORQUE_UNICODE

Now everything compiles, but the linker fails to find some calls. I guess there are some .cc files missing in the makefile.

#10 From what i am understanding, the new directory for the vorbis files is in the xiph folder.
Wouldn't it be better to alter any files to point to the xiph folder instead of adding old files?

What files is the linker missing?

#11 @david: sure, I didn't know where to put the vorbis files, but the compiler finds them now.
Well, the linker doesn't directly say that it is missing files, it complains about missing methods. This is too much to post here, but one example:

out.GCC3.DEBUG/game/fps/guiClockHud.obj(.data$_ZTV11GuiClockHud+0x108):d:/torque/engine/game/fps/guiClockHud.cc:48: undefined reference to 'GuiControl::findPrevTabable(GuiControl*, bool)'

#12 Try applying the patches listed in this thread www.garagegames.com/mg/forums/result.thread.php?qt=34348

#13 Ok, this brought me back to square one. Now it complains again, that audioFunctions.cc wasn't working right, which I fixed by copying the vorbis folder. Where do you guys place the vorbis folder?

#14 You gentlemen may be pursuing this all a bit prematurely. After all 1.4 is immenent. (C;

#15 Imminent, like in it's not there yet, and no one knows when it's here. After all I am tryingo to make it work now. If wonder if someone managed to get this to work, and obviously Benoit did, so I have to apply the solution he provided correctly.

#16 All i did was apply what had been done or mentioned by gregory and made a mega size patched from it all. But yes it does work here now :P

#17 Does somebody know if where the changes between 1.3 and 1.4 are listed?
I haven't managed finding any webpage about this yet =/

Thanks in advance,

Isi

#18 I also would love to find a simple changelog.txt file somewhere, but there's much more information on the changes on other news sites than in the GarageGames site.

I only knew it was out, because I read about it in another site (I'm downloading it right now).

#19 If you really want to keep a solid heads up on TGE and what's new, make sure to keep your eyes peeled for Ben Garney's .plans.

He's basically the GG "Build Guru" for TGE these days, and if anyone is truly "in the know" with regards to upcoming changes, it's him.

I'd wager most of what you're reading on other sites about TGE is straight out of his blogs in the first place. (C;

#20 1.4?

Thats old news!... I need TGE 1.5 before I can even think about working on my game.

Is 1.5 out yet?