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

Editline can't work under MSVC #786

Open
xiangxn opened this issue Mar 26, 2018 · 9 comments
Open

Editline can't work under MSVC #786

xiangxn opened this issue Mar 26, 2018 · 9 comments
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2f Testing Status indicating the solution is being evaluated against the test case(s) 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5b Docs In Progress Status specific to Documentation indication they are currently being refined 6 Build Impact flag identifying the build process build About build process feature

Comments

@xiangxn
Copy link

xiangxn commented Mar 26, 2018

Editline can't work under MSVC

@jmjatlanta
Copy link
Contributor

I believe the readline/editline libraries only worked in *nix-type OSs. And that continues to be the case. Is it causing a compiler or runtime error? Or is it simply not working?

If it is a compiler or runtime error, it will need to be fixed quickly.

If the functionality is simply not there, we will have to wait until editline code for Windows is developed and implemented.

@abitmore
Copy link
Member

It doesn't compile due to use of sys/ioctl.h and etc. I'd suggest that we skip compiling it for now. I'm working on a patch.

@jmjatlanta
Copy link
Contributor

jmjatlanta commented Mar 26, 2018

I believe one problem is bitshares-fc's CMakeLists.txt line 117. Removing "COMPILE_DEFINITIONS" allowed cmake to run. Still testing.

@xiangxn
Copy link
Author

xiangxn commented Mar 27, 2018

You can consider using wineditline instead of editline in windows, but you have to modify a lot of code, or give up some functions.

@xiangxn
Copy link
Author

xiangxn commented Mar 27, 2018

If there is time and manpower, we should use MSYS to compile the execution files under Windows, so that the initial work will be larger, but there will be less cross-platform compatibility issues.

@abitmore
Copy link
Member

@jmjatlanta how did it compile for your?

libraries\fc\vendor\editline\src\editline.c(25): fatal error C1083: Cannot open include file: 'sys/ioctl.h': No such file or directory

@xiangxn check this: #738, it's even easier.

@abitmore
Copy link
Member

abitmore commented Mar 27, 2018

I want to skip editline in MSVC so far: bitshares/bitshares-fc#34. Please check.

By the way, please check bitshares/bitshares-fc#32 as well, which enables building with GCC 4.8.

@jmjatlanta
Copy link
Contributor

jmjatlanta commented Mar 27, 2018

Your change bitshares/bitshares-fc#34 works with MSVC.

@abitmore abitmore added build About build process feature labels Mar 29, 2018
@abitmore abitmore added this to the Future Non-Consensus-Changing Release milestone Mar 29, 2018
@ryanRfox ryanRfox added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2f Testing Status indicating the solution is being evaluated against the test case(s) 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5b Docs In Progress Status specific to Documentation indication they are currently being refined 6 Build Impact flag identifying the build process labels May 24, 2018
@jmjatlanta
Copy link
Contributor

jmjatlanta commented May 25, 2018

Check out https://github.com/AmokHuginnsson/replxx

Small, BSD licensed, compatible with Linux, Mac, and Windows.

Update: It seems the UTF-8 portion of replxx uses a header that is not BSD compatible. Researching to see if there is a fix for this or a different library with similar functionality.

@jmjatlanta jmjatlanta removed their assignment May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2f Testing Status indicating the solution is being evaluated against the test case(s) 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5b Docs In Progress Status specific to Documentation indication they are currently being refined 6 Build Impact flag identifying the build process build About build process feature
Projects
None yet
Development

No branches or pull requests

4 participants