-
Notifications
You must be signed in to change notification settings - Fork 27
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
Build Error #5
Comments
Yes, for now makesystem is dumb and doesn't do much to work with non-standard library installation paths. AFAIK libwebsockets installs by default to /usr/local, not /usr, so you can try installing libwebsockets to /usr as the plugin expects, to do so, use
This error, however, is not related to libwebsockets and looks like you have a rather old version of bitlbee. |
Oh, you specified bitlbee's version and 3.4.1 should have required structure. If the error still there when all libwebsockets errors are gone can you please post the output of the following command:
|
Hmm, looks like it installed to /usr/local/include/bitlbee/json.h. So I rebuilt bitlbee's dev files with:
Then I ran Do I have to reinstall the entire bitlbee binary to the new /usr path as well? |
Did you do the stuff from my firs comment? Is there a /usr/include/libwebsockets.h? |
Ah, yes. I rebuild libwebsockets with prefix=/usr.
I also tried the CFLAGS make, but still not working: https://gist.github.com/Kays/1588601e69e6421718b4
Really weird. |
Ok, json_value error is my own bug and it should be fixed by edffe8c. |
Made libwebsockets changes in commit 2d12954, should compile fine with latest libwebsockets now. |
Works! Thank you very much. One change that I had to make in Makefile is: BTW: Happy New Year to you! |
Do you know if there's a way to not have two channels with the same name across multiple Discord servers clash in bitlbee? Currently, it just names it subsequent ones with _ suffices. I'm thinking maybe even #server.channel convention can work? Just a thought. |
Happy new year to you too. Thanks for mentioning that install issue, commited a fix for that. As for channelnames collisions - there is no way to avoid this at the moment. I've been thinking about server_channel convention, but from what I saw server/channel names tend to be quite long, so I definitely don't want this convention to be applied by default, I might implement it as an option though. |
Hello,
First, I want to thank you for your work.
I am trying to build it but I am running into an error. (BitlBee version 3.4.1.) I started with libwebsockets and that went well via these commands:
Then proceeding to build bitlbee-discord:
Not sure how to move forward from this. Any help is appreciated. Thank you!
The text was updated successfully, but these errors were encountered: