Page 1 of 2

Porting is such a pain in the ass

Posted: Tue Mar 28, 2017 6:47 pm
by praetor242
If I do another

./configure
./make
./make install

one more time, I'm going to loose it :P

I have gotten better with it though. I have all the most recent GNU build utils running, most recent SSH, Python 2.7.13 almost working, and gonna tackle the latest glib2 and from there gtk. I'm sure I can get gtk2 working, gtk3 might be a challenge. But from what I've been reading it's certainly possible

I'd like to package some of this up for the community, but I'm afraid it will cause conflicts with nekoware. I hate to have a fork of it, because install locations would be different and maybe some hurt feelings. I dunno. You guys can tell me what you want.

Porting is definitely a labor of love though.

Re: Porting is such a pain in the ass

Posted: Tue Mar 28, 2017 7:47 pm
by Raion-Fox
Don't bother with GTK3, it requires dbus. Focus on GTK2, QT, and other out of date software.

Post your patches here and someone will package them up and put them in Nekoware.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 1:24 pm
by foetz
Raion-Fox wrote:Post your patches here and someone will package them up and put them in Nekoware.

it's not that simple.


praetor242, much thanks for your efforts and offer. there're several ways of contributing your stuff. you could:
  • have a look at the nekoware faq in our wiki and wrap things up accordingly
  • offer them as independent packages. if you wanna do that more often you could also ask neko for a folder in our contributors area
  • offer them completely independently i.e. hosted by yourself, built by your rules and just providing the links

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 1:41 pm
by praetor242
I can host them on SDF and offer links. I'm packaging things according to that wiki page (http://www.nekochan.net/wiki/Packaging_Software) but the install location is /usr/local/* so as not to interfere with nekoware. Right now I have the recent gnu toolset compiled, I'm working on gtk2 so I can get the updated pidgin working, but taking a break from that because glib is angering me :p So right now I'm giving weechat a stab which will at least give my O2 something useful to do.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 2:22 pm
by Raion-Fox
Irssi is another thing.

Foetz I can definitely package some stuff he posts if he puts make/configure patches up here. I'm down with doing nekoware packages now because I've figured out its too monumental to do something on the scale of nekoware on your own.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 2:58 pm
by foetz
praetor242 wrote:I can host them on SDF and offer links. I'm packaging things according to that wiki page (http://www.nekochan.net/wiki/Packaging_Software) but the install location is /usr/local/* so as not to interfere with nekoware

alrighty that's fine. then they'd be independent packages. very welcome of course :-)

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 3:52 pm
by praetor242
Nou...irssi sucks

Yeah. I'm not out to replace nekoware. It would be a big deal. But yeah, being able to contribute what I port would be cool.

Independent packages it is :D

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 4:57 pm
by Raion-Fox
wechat sucks IMHO.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 4:58 pm
by praetor242
I'm afraid we'll just have to agree to disagree ;)

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 5:07 pm
by Raion-Fox
Weechat's issue for me is GPLv3. I'm avoiding that like the plague when possible. Compiler/binutils don't bother me much but I willingly switched to i3 when my chosen windowing system at the time adopted GPL3 for future releases. Is there a stylistic reason you don't like irssi, or is it related to interface, config, key commands etc?

As for everything else feel free to use the access to my server to host, as well.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 5:12 pm
by praetor242
I just don't like irssi. It's not really as intuitive as weechat is.

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 5:12 pm
by Raion-Fox
Okay. Vim, pico or EMACS?

Re: Porting is such a pain in the ass

Posted: Wed Mar 29, 2017 5:32 pm
by praetor242
Easy. Vim :3

Re: Porting is such a pain in the ass

Posted: Thu Mar 30, 2017 11:13 am
by foetz
you might wanna make a new thread for "which app do you prefer" :P

Re: Porting is such a pain in the ass

Posted: Thu Mar 30, 2017 12:37 pm
by praetor242
Some of this I need to redo, because when I started, I didn't know as much as I do now, and compiled it for mips3. Oops. Probably not a big deal, but not as efficient. I've been reading everything I can get my hands on about MIPSPro, and when things don't work out right, I've taken to individual project's IRC channels. I either get mild confusion, or all out excitement. :p

But once I target what I have for mips4, I'll start putting this up on SDF