[Solved] Compile issues with a Feathercoin Fork
-
@UnklAdM I used to have the same problems but I have compiled successfully. Make width and height in the source file public and that is it, build will pass and wallet will work :)
9
Btw this is the problem when you compile on linux (depends on zxing - i have take the source of some another project on github - forgot its name) only and is caused when you want to build the qt wallet.Cheers :)
-
Thanks… I got this working on Centos 7, here’s what I did…
As advised, I made width and height public in ./zxing/LuminanceSource.h
As Centos 7 (and Red Hat) lack the ec_curve cipher in openssl, I applied this patch to src/key.c
http://pastebin.com/raw/iFYJsgus
Then I manually replaced all remaining occurrences of
EC_KEY_new_by_curve_name(NID_secp256k1);
with
EC_KEY_new_by_curve_name_NID_secp256k1();
Surely an ugly hack, but the wallet is now syncing…
;)
Note: I cloned zxing from https://github.com/glassechidna/zxing-cpp.git into the Feathercoin subdir then
cd src/qt
ln -s …/…/zxing-cpp/core/src/zxing zxing -
Glad to see, that you made it :)
-
hey everyone i just saw all the replies here, the person i was compiling for gave up and switched to a different source code which did not use the zxing, but now i have someone else asking me to compile a wallet and am getting this error again
first to answer the old question, no i was NEVER able to compile it and i was NEVER able to find a copy of zxing that mingw would find or use, i have also NEVER been able to compile windows wallets on linux which is why i compile on windows wallets on windows and mac on mac etc
i have also tried using the --with-qrcode=no and it does not work, if anyone has any advice they can give please let me know.
-
I don’t have windows, but we have been doing a lot of work with version 0.9.3.2 around dependencies. I’ve updated some build instructions. You could see if that helps.
https://github.com/wrapperband/Feathercoin/tree/0.9.3.2/doc
I know our Dev Lizhi is managing to compile the Windows version, however, he is in China, so we’ll need to wait for him to be able to respond.
If you try the Windows build and checkout 0.9.3.2 (with some build improvements over 0.9.3.1) - let us know what happens, so we can try and duplicate your issue.
It is backwardly compatible and a proposed maintenance release soon.
-
@wrapper said:
I don’t have windows, but we have been doing a lot of work with version 0.9.3.2 around dependencies. I’ve updated some build instructions. You could see if that helps.
https://github.com/wrapperband/Feathercoin/tree/0.9.3.2/doc
I know our Dev Lizhi is managing to compile the Windows version, however, he is in China, so we’ll need to wait for him to be able to respond.
If you try the Windows build and checkout 0.9.3.2 (with some build improvements over 0.9.3.1) - let us know what happens, so we can try and duplicate your issue.
It is backwardly compatible and a proposed maintenance release soon.
i went through all the links in the link you posted and the only time i saw zxing in there was for unix/linux and nothing in there about compiling on windows, im compiling using mingw and msys
-
@ironsniper I don’t have Windows. Sorry it didn’t help.
There are specific Windows build instructions, if you follow those and tell us where it went wrong we can try to help (though), it “all doesn’t work” doesn’t really help find a solution.
g’night. -
if there is one just for windows i am not seeing it and nothing with zxing in it except for the linux/unix ones and the error comes up during the ./configure and it complains about not finding zxing no matter what i try
-
There is a little bug in the configure script. It should not enable use_qr if no zxing is found:
--with-qrcode enable QR code support (default is yes if qt is enabled and libzxing is found)Run ‘configure --with-qrcode=no’ and it will compile.
The wallet will be fully functional, only no qr codes can be scanned.
-
@Wellenreiter said:
There is a little bug in the configure script. It should not enable use_qr if no zxing is found:
--with-qrcode enable QR code support (default is yes if qt is enabled and libzxing is found)Run ‘configure --with-qrcode=no’ and it will compile.
The wallet will be fully functional, only no qr codes can be scanned.
i have tried --with-qrcode=no and it still tries to find zxing
-
Is it during the configure step or the compile?
It seems that you are using a different code than I do.
can you check with ‘./configure --help’ if there is a --with-zxing=no option?
Also for me to better understand, so please forgive that question:
what exactly did you do to compile the code?
The normal way is to download or clone the code from github and then run
- ./autogen.sh
- ./configure [–options]
- make
By the way, if you are compiling for others, not for yourself, why not using the ‘official’ binary, that is available from the resources section of www.feathercoin.com?
The direct link to the downlaod is https://github.com/FeatherCoin/Feathercoin/releases/download/v0.8.7.3/feathercoin-qt.exe
-
@Wellenreiter said in compile issues:
Is it during the configure step or the compile?
It seems that you are using a different code than I do.
can you check with ‘./configure --help’ if there is a --with-zxing=no option?
Also for me to better understand, so please forgive that question:
what exactly did you do to compile the code?
The normal way is to download or clone the code from github and then run
- ./autogen.sh
- ./configure [–options]
- make
By the way, if you are compiling for others, not for yourself, why not using the ‘official’ binary, that is available from the resources section of www.feathercoin.com?
The direct link to the downlaod is https://github.com/FeatherCoin/Feathercoin/releases/download/v0.8.7.3/feathercoin-qt.exe
i am not compiling feathercoin its a coin based off the feathercoin source code, there is also no option --with-zxing=no and this is the error i get during the configure part
configure: WARNING: libzxing not found; coin-qt frontend will not be built
i am sure if i could find the correct one and figure out where to put the files so it will see it i am sure i can get it to compile
-
I’m not sure quite what to say, it would be impossible for even Albert Einstein to diagnose a problem without the relevant information.
I pointed out we need to know what was done and the output to help, it turns out it wasn’t even a Feathercoin build? ¯_(ツ)_/¯
- If you point us to the Github, and give us the output, someone might be able to help.
- The subject should have been brought up in an “Off Topic” thread, or at least in “Support” with the full details of which coin it is. Members have helped other coins before (Litecoin, Phoenixcoin, Catcoin, UFOcoin, etc)
- You could apply to add a Coin-Qt in the Alternative coins section of the forum and build up some community support there.
-
this is a new coin that has not been released or announced yet, but the coin itself doesnt matter, when i first made this thread i was working on voxels which was using the feathercoin source code, but because of that zxing error the dev switched the source code to something that was easier for me to compile but now i have someone asking me to do a wallet using this source again and i still cant figure out how to add zxing to my deps for compiling so that the ./configure option will see it
i guess my main question is how do i get my compiler (mingw/msys) or the ./configure to look for and find zxing so it can be used
-
@ironsniper said in compile issues:
i guess my main question is how do i get my compiler (mingw/msys) or the ./configure to look for and find zxing so it can be used
http://forum.feathercoin.com/topic/8570/dev-release-candidate-feathercoin-0-9-3-2-check-list/34
check that post I made for replicating in Ubuntu, read the whole thing but please use the 0.9.3.1 if you’re going to test with Feathercoin. I gave instructions for libzxing
-
@aciddude said in compile issues:
@ironsniper said in compile issues:
i guess my main question is how do i get my compiler (mingw/msys) or the ./configure to look for and find zxing so it can be used
http://forum.feathercoin.com/topic/8570/dev-release-candidate-feathercoin-0-9-3-2-check-list/34
check that post I made for replicating in Ubuntu, read the whole thing but please use the 0.9.3.1 if you’re going to test with Feathercoin. I gave instructions for libzxing
is that for compiling for windows or linux? cause i am compiling for windows on windows not linux
-
@ironsniper said in compile issues:
@aciddude said in compile issues:
@ironsniper said in compile issues:
i guess my main question is how do i get my compiler (mingw/msys) or the ./configure to look for and find zxing so it can be used
http://forum.feathercoin.com/topic/8570/dev-release-candidate-feathercoin-0-9-3-2-check-list/34
check that post I made for replicating in Ubuntu, read the whole thing but please use the 0.9.3.1 if you’re going to test with Feathercoin. I gave instructions for libzxing
is that for compiling for windows or linux? cause i am compiling for windows on windows not linux
Yep I see that. Just worth pointing out even when I had the zxing folder in my source it was still looking for two other files… Maybe windows is doing something similar ?
-
@aciddude so you put the zxing into the source for the wallet? does it go in any particular folder or? maybe thats why it cant find it, cause i have no idea if i have the correct files for zxing or if i am evern putting them in the correct place as i cannot find anything coins besides feather that has this thing
-
What is the feathercoin code base/github/branch you used to fork the new coin and did you change any of the .m4 files or files under the diffenrent m4 directories?
With the feathercoin code base I can check the FTC configure script and the ac-files and if we have the same bug there, I probably can fix it, in a way, that you can disable qr support and compile the gui
-
@Wellenreiter said in compile issues:
What is the feathercoin code base/github/branch you used to fork the new coin and did you change any of the .m4 files or files under the diffenrent m4 directories?
With the feathercoin code base I can check the FTC configure script and the ac-files and if we have the same bug there, I probably can fix it, in a way, that you can disable qr support and compile the gui
i have no idea what version atm, the person gave me access to a private github with the source and just asked me to try and do a compile
