Making an .exe

Hello, I have a program that I made in Dev, and I want to post it on a site for people to try. But I wouldn't know how to do that. In other words, I don't know how to make an executable file. I want it so people can't see the actual code, and don't need a compiler to run it. If anyone knows how to do this than tell me. THANKSSSS.

When you compiled the source code an executable would have been created in the same folder as the source code

OK. So will I be able to post that executable on a site or something, without people seeing my code?.

just upload your .exe and keep your source code.

Originally Posted by Sentral

OK. So will I be able to post that executable on a site or something, without people seeing my code?.

Yeah, they'll only be able to run the exe and not see any of your juicey code :P

Awesome. You know I'm a newb when I ask that. I am making a 1337 translator right now, and I'm hoping to post it up on a site. If you don't know what 1337 language is than this will help you . It's somewhat of a joke program. But I am making it for the experience.

Originally Posted by Sentral

Awesome. You know I'm a newb when I ask that. I am making a 1337 translator right now, and I'm hoping to post it up on a site. If you don't know what 1337 language is than this will help you . It's somewhat of a joke program. But I am making it for the experience.

I think all of us have tried our hand at that or something similar... another fun idea: try reproducing what's in my sig (the "is there..." link, not the function).

hint: internet colors are made up of the following: #RRGGBB and it's a hex number. in case you don't know the hex numberline: 0 1 2 3 4 5 6 7 8 9 A B C D E F

here are some example colors:
#FF0000
#FF9900
#FFFF00
#00FF00
#0000FF
#FF00FF
#000000

Just an interesting aside, I'm not sure who specifies this, but it's been said that at the very minimum, internet browsers should be able to correctly show the colors specified with the hex digits 0, 3, 6, 9, C, and F - so for the purposes of browser compatibility - you'll usually see those colors uses. major_small's example consists entirely of those combinations.

On the question of people being able to see your source code or not, remember that there's rarely if ever a way to completely stop someone from cracking your program. When you distribute your executable, you're distributing the binary machine instructions that the computer understands. It's very easy to convert that into assembly code. From that point on, it gets quite difficult to convert your code into a higher-level language, but assembly is workable. One precaution is called obfuscation (unless I'm confusing my big words). You can get programs (or just do it yourself) that will change all your variable and function names from words that make sense to you as a coder, into sequences that are hard to read or make the program confusing - do that to your code before compiling and you're a little safer. A common method is to use sequences of capital O's and zeroes, making for unique, but barely readable names, like O00O0OO instead of "password" - it's just one way to be safer.

that just makes it harder on you... to the compiler it all looks the same... and it all gets compiled into the same machine code.

Code:

#include<iostream>

int main()
{
        std::cout<<"Hello World"<<std::endl;
        return 0;
}

is the same as

Code:

#include<iostream>

#define o00000  int
#define o0000O  main
#define o000O0  ()
#define o000OO  {
#define o00O00  std::cout
#define o00O0O  <<
#define o00OO0  "Hello World"
#define o00OOO  std::endl;
#define o0O000  return
#define o0O00O  }

o00000 o0000O o000O0 o000OO o00O00 o00O0O o00OO0 o00O0O o00OOO o0O000 0; o0O00O

after it gets through the preprocessor, and if you're just talking about variable names, then it makes even less of a difference.

I've decided to do something a little different. Making a translation of the language would be a little to hard for me. So instead I am making a library of online languages, to allow the user to understand and store different key phrases. Such lol (laughing out loud), etc. I am just not ready for handling that sort of thing.

I wasn't intending it to be changed with the preprocessor. The specific example I'm thinking of is a tool that comes with VS.NET that will make changes to the actual source file.

maybe, but the way you described it, it wouldn't make a difference (just changing variable and function names)