Writing an executable writer c++/c#

Question

2.00/5 (2 votes)

See more:

Hello Forums

I am writing a 2D game engine and have got to the stage where pretty much everything is done other than an executable exporter. I need some idea on how to write an executable file via either C++ or C# rather than just saving it to the engine's own format.

Any ideas or code snippets? :)

Posted 6-Jul-13 8:11am

chlohee

Add a Solution

Comments

Sergey Alexandrovich Kryukov 6-Jul-13 15:35pm

Not clear. What is "executable exporter"? What it is supposed to do?
Do you want to create and load executable files during runtime? If so, why?
—SA

chlohee 6-Jul-13 15:42pm

Create executable files on runtime so games can be played by normal people without the engine.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

pasztorpisti · Accepted Answer · 2013-07-06T10:11:00

You shouldn't write an executable exporter. You should export the game data of each game that can be used by the very same executable. After this you can pack the data for example into a zip file and you can append it to the executable if you want a single-file game. If you are concerned that every game needs some kind of game logic as well: The game data may contain scripts for the script engine(s) of your game provided by the executable. One of my favorite scripting engines is the flowgraph of CryEngine (similar to the Kismeth of UnrealEngine) - it is just a graphical graph in the editor that can be serialized to any format, for example to xml, text, json, anything...

Writing an executable export has several other disadvantages: For example antivirus software probably wouldn't like it while in case of a single executable you build it at home you can sign it and leave it as it is.