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

Running and building rmw on Windows #71

Open
andy5995 opened this issue Oct 25, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@andy5995
Copy link
Member

commented Oct 25, 2016

Using CygWin, I built a Windows binary for rmw. It's available in the win32 on the develop branch.

Instead of HOME, it uses the environmental variable LOCALAPPDATA.

Anyone wanting to experiment with it can find their LOCALAPPDATA directory by using the set command. On Windows, rmw should create a trash folder there (.trash/rmw/files & .trash/rmw/info), and create a configuration directory in %LOCALAPPDATA%

  1. copy rmwrc to %LOCALAPPDATA%\rmw and rename it to config
  2. Place rmw.exe and cygwin1.dll somewhere in your path

Problems I've had so far:

  1. Doesn't create the .trash/info dir until the second time it's run.
  2. When I restored a file after using rmw, it sent it to the correct path, but it used the cygwin path of /cygdrive/c...

If you try building from source, you'll need to #define WIN32 in the CFLAGS option, or at the top of rmw.h.

I'm not writing out complete instructions yet until I've tested it more and added a bit more code to ensure portability. Nothing is in place yet for make install.

Anyone wishing to help me get that code in place or test, please let me know.

@andy5995

This comment has been minimized.

Copy link
Member Author

commented Oct 14, 2017

If anyone is interested in doing this, do you think using Cygwin is the best method? I'm open to other ideas.

Please remember to "star" this project (upper right corner) and join the chat room if you like.

The Contributing wiki page contains important information about making pull requests.

@sexybiggetje

This comment has been minimized.

Copy link
Member

commented Nov 27, 2017

AFAIK, for a native executable Cygwin is the easiest and best method. I dislike the extra dll, but it's already in my "unixutils" folder anyway.

Nowadays however you have a full linux system running if you want with WSL. Basically what WINE does for Windows on Linux, WSL does for Linux on Windows. Best thing of all, it's just an optional install. WSL compiles a working Linux binary.

@andy5995 andy5995 added pri:low and removed pri:normal labels Nov 28, 2017

@andy5995

This comment has been minimized.

Copy link
Member Author

commented Nov 28, 2017

AFAIK, for a native executable Cygwin is the easiest and best method.

I agree. I have very little experience with Windows programming, but from what I do know, Cygwin is the way to go.

I'm glad I documented some of my experience with building and running it on Windows in the first post. That was over a year ago.

I have no plans to do anything with this, but if anyone has some experience with Windows programming and wants to implement this, please do so. :)

@andy5995

This comment has been minimized.

Copy link
Member Author

commented Jan 10, 2018

Regarding getting the right path or HOME info, this might give some clues when we work on this in the future:

https://github.com/MegaGlest/megaglest-source/blob/12998eb10f6447ac89a45d1e6d76f17946647b7a/source/shared_lib/sources/util/properties.cpp#L214-L265

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.