Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pack into native application files #32

Open
williambl opened this issue Feb 10, 2016 · 9 comments
Open

Pack into native application files #32

williambl opened this issue Feb 10, 2016 · 9 comments
Assignees
Milestone

Comments

@williambl
Copy link
Member

Self explanatory. .exe and .app, and a linux application too.

@williambl williambl added this to the 2.1 milestone Feb 10, 2016
@Valiec
Copy link
Contributor

Valiec commented Apr 12, 2016

For windows, you probably want to use py2exe.
For OSX, you probably want py2app.
For linux, it is different between different distributions, but for Ubuntu/Debian, try py2deb.

Since these are all tools that must be run on the source files before each release, you may want to make some sort of build script for CMAN. In terms of build tools, PyBuilder looks to me like it might work.

I'll see if I can get this working.

@Valiec Valiec self-assigned this Apr 12, 2016
@Valiec
Copy link
Contributor

Valiec commented Apr 15, 2016

Actually, it turns out you can't build a windows .exe with py2exe in an OSX environment (which is what I'm using). I'm still testing Linux.

@williambl
Copy link
Member Author

I have a Windows partition, I could build with that. I also have a Linux partition which I could build with.

And a mac. Perhaps I should do the building?

@Valiec
Copy link
Contributor

Valiec commented Apr 16, 2016

Thanks! I'll try to get the setup.py files for windows and Ubuntu finished, then give them to you (though if you don't really want to do the building, I also have Windows, OSX, and Linux systems and could build).

@williambl
Copy link
Member Author

I'll do it. Does the OSX build require a setup.py?

@Valiec
Copy link
Contributor

Valiec commented Apr 16, 2016

It does. Since I don't have a dedicated place set up for this build stuff yet, here's a pastebin with the OSX setup.py: http://pastebin.com/HT43V8qG

To use it, put it in the same folder as all the sources. It will build.

However, I found that it now errors whenever it tries to do input() on the console, it crashes with an "EOFError: EOF when reading a line" error. Apparently, the built version doesn't support console input. So actually all uses of input() that are used when the gui is enabled (there are nine of them, all in CMAN_util.py) must be removed (and replaced with dialogs) from the GUI version, which also must be made the default, before the build will actually run.

@williambl
Copy link
Member Author

williambl commented Apr 16, 2016

OK, thanks.

@Valiec
Copy link
Contributor

Valiec commented Jul 4, 2017

Sorry about leaving this for a year! I think that for now we should just release the version with the GUI, and then worry about trying to make native app files (I think that I found out it's somewhat tricky).

What do you think?

@williambl
Copy link
Member Author

Sounds like a good idea. I feel that what's actually holding us back right now is the fact that we have barely any mods in our repository - most people will not download a mod manager that doesn't manage all the mods they have. In a few days I'll add some more mods to the archive, then we can fix the bugs in the GUI version (there are quite a few) and release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants