MacroQuest64

Lax,

I have 4 computers here at my home, I will certainly be compiling for all 4 machines based on your new auth code (great idea btw)

Could you perhaps develop a "keyring", so that I can make 1 binary that works on those 4 machines?

Perhaps you could make the keyring limited in size, so that you can only put 6 computers max into a ring. Then I can take my "authorized" machines keyring, drop it in to save some time (since we aparently will have to compile more often now as well).

-Zx

Feel free to keep a copy of the .h for each machine, though we may opt to change it from time to time so I can't guarantee that'll work forever

Keeping a copy of the .h isnt the problem though. Sitting there copying four .h files in, recompile, take the results out, copy them to the target machine. Now do that 4 times. That is the problem.

I would like 1 binary that works on all four machines.

But I only need to create the .h file from the Auth one time, keep a copy of the .h for each of my machines and just compile it for each different machine?

Sounds easy enough... If I only need to make a .h one time...

Now, what if my machines are all identical, same hardware, same OS, same OS key.. do I still need different .h files for each?

Bob

The .h is machine specific. You need to make one ON each machine, then compile FOR each machine. Compiling can be done on any comp, but the build will be machine specific.

Pain for me too since I'm using 3 comps, but nothing that can't be dealt with.

And I can keep the .h file run from each machine indefintly or do I need to create a new .h file for each machine everytime a new MQ2 is released for compile?

Correct, a "pain", but worth the effort.

Yes, like Mckorr said, nothing that cant be dealt with, but still annoying, I mean Macroquest is supposed to save us time right?

I suppose I could come up with some sorta batch script, to copy the .h file in and compile, copy out the results, then copy in the next .h but I thought we left batch scripts when we ditched DOS and that a keyring would be more elegant.

I cant see how this would be hard either, you have 1 key file with all the computers you use, and just let your binary work with all those keys...

It would be easy to code, not worth a major debate over, and it will make MQ2 perform a little more like a robust program.

Bob, just need to make your .h file 1 time on the machine, you can keep it forever, or until you die whichever comes first.

Even with a keyring you'd still have to go to each machine to generate the .h file initially.

I'm sure something can be worked out along those lines though, so you would only have to recompile once after a patch, instead of once for every machine. Correction, you'd have to recompile MQ2Main. Lax is quiet today, so I assume he's busy with work. Give him a chance to consider it.

As for batch files, you could probably come up with a macro in VS to handle all that for you if you don't want a console batch file to do it.

Zxeses wrote:I suppose I could come up with some sorta batch script, to copy the .h file in and compile, copy out the results, then copy in the next .h but I thought we left batch scripts when we ditched DOS and that a keyring would be more elegant.

Ha, ha.

Perl

JavaScript

VB Script

DOS

One of these thing is not like others, one of these things just doesn't belong.

Learn the ways of nmake, Grasshopper, and add scripting to your resume..

Hmmm... I can make it work the way you want.

Rather than playing with nmake and scripting, and still having to keep up with 2 separate compiles, modify the source to accept up to 5 different machine defines in the mq2auth.h file. You'd still have to produce the mq2auth.h file for each machine, and then modify the file in the source directory to include the define for each one according to the dev's specification, but that would be a one time process, which would allow that binary to work on the 5 or less machines who's machine hash's are in the code.

This is particularly attractive, as MQ2 is still being changed, quite often, and is sometimes being compiled several times a day. Not having to recompile for each machine separately because each machine is already defined in the .h file would be a big help :)

- TI

my only complaint is that i don't want to have to install VS.net on 5 more machines.

You don't have to. You didn't have to under the original authorization scheme either. You only had to run the mq2auth.exe on the 2nd machine to generate the .h file, which could be copied back to the compile machine.

Thanks for adding in keyring support Lax!!! Will be huge benefit for those of us with multiple machines!

- TI

40oz, you dont have to install VS.net on any more machines, read the instructions for compiling for friends / other computers.

Secondly, the system has been updated this morning to address the concerns presented in this thread and elsewhere. Please read the new instructions for compiling for friends / other computers.

The instructions are found here: http://macroquest2.com/phpBB2/viewtopic.php?t=4132