Author Topic: New Sdk Needed!  (Read 2140 times)

Offline HaXtOr

  • Sr. Member
  • ****
  • Posts: 423
    • http://www.wtfmoogle.com
New Sdk Needed!
« on: October 04, 2005, 05:24:37 PM »
Would it be possible to create a new sdk useing asm ? also i would love to see a new sdk made that has supposrt for command packets taht works on my computer

Offline Eddy-B

  • Hero Member
  • *****
  • Posts: 1186
    • http://www.eddy-b.com
New Sdk Needed!
« Reply #1 on: October 04, 2005, 05:36:16 PM »
doesn't the code i wrote work for you hacker ?
i'd like to know if you're having problems with it!
Rule #1:  Eddy is always right
Rule #2: If you think he's wrong, see rule #1
--------------------

Outpost : Renegades - Eddy-B.com - Electronics Pit[/siz

Offline Hooman

  • Administrator
  • Hero Member
  • *****
  • Posts: 4955
New Sdk Needed!
« Reply #2 on: October 04, 2005, 07:30:05 PM »
You don't really need an SDK if you're using asm. The SDK is mostly just to get the compiler to link your code correctly with the OP2 code. But since there is no compiler with asm....

 

Offline HaXtOr

  • Sr. Member
  • ****
  • Posts: 423
    • http://www.wtfmoogle.com
New Sdk Needed!
« Reply #3 on: October 14, 2005, 05:43:34 PM »
What about a template?

Offline Hooman

  • Administrator
  • Hero Member
  • *****
  • Posts: 4955
New Sdk Needed!
« Reply #4 on: October 15, 2005, 05:03:50 PM »
I guess a template could be done. Why don't you look into it?  :o You might learn quite a bit from doing something like that. I remember hearing of a linker that could resolve exports/imports directly from the executable image you were trying to link to, so there would be no need for libraries. Maybe try googling GoAsm and GoLink or something like that. I'm pretty sure it had "Go" in the name. (I could be wrong).

The only ugly thing is that Outpost2 exports a lot of decorated names. So if the linker is going to find them, you'd need to type the decorated names exactly as Outpost2.exe exports them. Needless to say that's a huge pain in the butt. Maybe you can do something to allow for shorter/simpler names though.

On the other hand, why have something in asm? There isn't any real benefit to coding DLLs in assembly. Most of the code is in InitProc, and only gets run once for the initial setup. Even if you have lots of code outside of InitProc, speed still shouldn't be an issue. It seems like asm would mostly just make it harder or slower to write DLLs. That and you can always use the inline assembler in a C++ project. But then, I'm sure a download package for making DLLs in assembly would be really tiny.
 

Offline Eddy-B

  • Hero Member
  • *****
  • Posts: 1186
    • http://www.eddy-b.com
New Sdk Needed!
« Reply #5 on: October 16, 2005, 06:54:13 AM »
Quote
Most of the code is in InitProc
.. not im MY DLLs!
And speed.. yea. The main problem is Triggers: they slow down the game. I've experimented with them, and compared them speedwise to what i've written so far using Events, and the are just slow.
The only trigger i was not yet able to replace with an Event are victory/failure triggers. But i will be looking into that sooner or later.
Rule #1:  Eddy is always right
Rule #2: If you think he's wrong, see rule #1
--------------------

Outpost : Renegades - Eddy-B.com - Electronics Pit[/siz

Offline Eddy-B

  • Hero Member
  • *****
  • Posts: 1186
    • http://www.eddy-b.com
New Sdk Needed!
« Reply #6 on: November 04, 2005, 04:15:58 PM »
I've been working on the documentation of the OP2Events library.
As soon as it's ready i'll release it into the Outpost Universe :D

OP2Events documentation website (temperary link)
Rule #1:  Eddy is always right
Rule #2: If you think he's wrong, see rule #1
--------------------

Outpost : Renegades - Eddy-B.com - Electronics Pit[/siz