When compiling my "slightly" modified version of battlestar, by using the "make install" command (installing it), it complains about a dictionary. Please help me get rid of the complaints to the satisfaction of the package maintainers of Linux Mint. The whole goal is just to learn more about how to do things, until I check more about the license, I'm not going to distribute my code nor this code. This is just academic for now. I'll check whether the license "technically permits distribution" after learning how to do better at it. I'm sure it allows my modifications, if I choose NOT to distribute it. I "might" distribute it, if allowed to do that too. But for now, I'm only choosing to share the error messages, while I complete my learning task.

Tell me if you need them. If you tell me about compiling them for Linux Mint, when it's unmodified, it should work the same way, and that will be sufficiant. What errors, should I just "expect"? What commands should I enter? That's why it's under software and not programming. Like I said, just learning how to do this, for now. No interest yet in THIS program, and being serious.

No way that anyone could know, unless you link to the source code and makefile.

OK. I guess I'm only asking what it should look like if it is compiled by Linux Mint, I believe I used Ubuntu source code from what I think is standard repository, I know I modified, but I'm asking what the compile should be like when unmodified, if someone could know. With my changes, it should look the same unless I made an error. But I don't know if anyone knows or not. I'll see if I can check the license tommorrow, and see if I believe that I can distribute a modified version and if I didn't already screw up by modifying it, technically, though it is meant for experience and fun, not real use. I could see myself rewriting from scratch at a later time, as a more serious project, if allowed. Maybe later today even, I can check that. If allowed, I would NOT mind making a repository for my work, and linking there. I just don't want to purposely break a license just for fun, if it says not to distribute modified copies, which I don't believe it says, but I just want to make sure.

You can answer the first question by simply compiling the unmodified version on your system, then you will know first hand. This will allow you to resolve any problems necessary to build on that system and provide the baseline for your modifications.

Then when you modify, make incremental changes and perform intermediate builds along the way to keep any new problems few and isolated.

Great idea! I can definately try compiling an unmodified version.

Sorry I haven't posted here in awhile. I guess I'll close, and I can always open a new thread. It's going to be awhile before I can work on this again. I am working on redoing servers a bit. In order to do that, I'm running into a new set of problems, which requires more additional learning. I'll get to this project, but it'll take awhile now. Therefore I'm closing this thread, so it doesn't automatically close anyway...