almiteycow

This would be the best way of doing it... not the easiest. It'll definitely be taken into consideration. However, at the moment, much of the focus will be directed at making a version of Apex that runs natively in Linux. EDIT: This may actually be a good direction to go toward: http://multidcpp.sourceforge.net/

If the client and GUI can be separated, people could make multiple front-ends for it. I'm not a pro-coder by any means, so I've gotta work with what I know... GTK. It uses scons, because that's what the linuxdc++ code that I'm merging with uses. If you'd like to autotool it, go for it. I'm going to see about sourceforging the files, so we can have a cvs to work off of.

If you guys can help port the network side, I can do the gui stuff. As long as there's a way to pass raw DC commands, we can test it. I'll post more tomorrow.

I can't edit my post? wtf? Anyway... Yep, I think the main() is supposed to go in the GUI.... I think. I'm stuck though look here.

Urgh. Looks like almost all of SharedFileStream.cpp needs to be rewritten for Linux. This is just the tip of the iceberg: client/SharedFileStream.cpp:42: error:

Yeah, that main thing is bugging the hell out of me, but I can't find it in the original code either. :S Will look into your suggestions on Monday. Thank you very much. Keep 'em coming :)

Woohoo! Thanks guys! It looks like we're generating some good attention to the project, from the buzz I'm hearing various places on the net. LinuxDC++ is the port of regular DC++, but I've heard rumours that they'll probably not work with us. They're working on porting the base DC++ only, no special Apex features and that sort of thing. Difference of opinions I guess (but that's the beauty of open source software, choice), best of luck to them anyway. It's a good baseline to work off, but some of the more advanced features we offer in Apex are derived from RevConnect, which seems to be really linux unfriendly code. Let us know what you find out, Anarion. Once again, thanks for the support, both monetary and kind words.

Well, after a nice little break, I've picked the project back up again. Kinda lost track of where I am, but I think I can figure it out. Looks like I was working on fixing linker errors, like these: Here's the latest source folder I'm using. Too lazy to clean it up, everything should be here, minus the dependencies. http://almiteycow.homeip.net/pub/linuxdcpp.tar.gz EDIT: Ah, nope, still working on porting those last 4. The scons file has 3 of them commented out.... they need to be put back in, and they throw the usual errors. EDIT: I found this! It should make life a lot easier for me.

Bingo Greg. That's what I'm hoping for here. You said what I was trying to say, better than I said it. I don't even know if I'll get a usable client out of what I'm doing (though that's what I'm hoping for), but hopefully we'll get some attention in the Linux community and one of them will come help us out. If not, I'll do the best I can until then, but don't expect beyond what the Windows client offers... if that. Notice we don't have a Feature Requests section for Linux? :P

Missed some files anyway, it seems. Getting a new compiler error: Argh.. RevConnect code is driving me nuts... To Port: FileChunksInfo.cpp SharedFileStream.cpp Text.cpp? TraceManager.cpp Then gotta fix random linker errors.

Lee, it won't build yet, due to the GUI stuff. I'll see if I can port the LDCPP GUI over real quick for testing.

Progress: Client is better, seems to be building alright, but that doesn't mean it's bugfree by any means, I know I've broken more than a few things. Now for the GUI... Things to check out before final release: Major: Need someone to audit the code, is there stuff that's obviously not going to work in the code? any glaring bugs? do i just plain suck at porting? Minor: PG support has been removed. It will need to be readded. Removed memcpy_amd, it doesn't like linux too much. This could cause problems later though. Removed webserver, will need to be readded. Changed RevConnect code - Will it work? Who knows? Morale: It be time to swab th' poop deck mateys!

Yup, Merry Christmas to you all. Being that I'm one of those last time zones to have Christmas, who knows how big the turkey is, or what I got. I'll know tomorrow. I do know that it'll probably never snow though. Best wishes from my warm desert.

Progress: (Slowly losing my mind) Even though I may have cleared a big hurdle with that RevConnect code, I'm continuing the $50 offer to anyone who wants to/has enough skill to A) Double-check my code so far and B ) Help with difficult porting problems, such as the one in this quote/error below. Post here with what you've got. We've got a few minor devs willing to help, which will definitely be handy while debugging the code, doing the GUI, and porting new features (and the ones I've had to remove) into future versions of Apex for Linux. I'm going to take a few days off from this, being on holiday and all if anyone wants to continue the project in the meantime, download the file posted earlier (apologies for the slow speeds, but it's coming off my home network), and overwrite the client folder with the one attached here, if all goes well and dependencies are met, you should receive this error: Things to check out before final release: Major: I don't know of an ADC hub for testing, need someone to find one and test for me. Need someone to audit the code, is there stuff that's obviously not going to work in the code? any glaring bugs? do i just plain suck at porting? Minor: PG support has been removed. It will need to be readded. Removed memcpy_amd, it doesn't like linux too much. This could cause problems later though. Removed webserver, will need to be readded. Changed RevConnect code - Will it work? Who knows? Morale: Argh, I be sippin' on the old grog, aye, I have. Oh! and .... Have a Great Christmas/Holiday Season/Whatever!

Support for both is already going to be hell... Especially since I don't know what I'm doing. As Grogs (deliberately [in]correct) said, I'm stripping out a bunch of stuff that can't be ported easily, as porting is already hard enough for me. I don't even know if I'll be able to keep up with Crise and his features on the regular client. I'd say that most likely it'll be the same as the basic Apex, if we're lucky and find a really good linux dev.

Yeah, I don't wanna see any errors coming out of SharedFileStream.h I'm not expecting the whole thing to compile. Yet. EDIT: Got it myself... See Post below.

It was giving my computer hell yesterday... but it was soo pretty.

I've got plenty of money. I can send it via PayPal, check, money order... hell, if you take credit card even... You'll get the money. Also, yeah, I know I'm offering money on an open source project; consider it a "bounty" as they have other places. I want this feature implemented, and I'm willing to pay. We may need to expand outside of our userbase though for this help. So, if you know any devs from other places/forums/hubs, let them know. If they don't get this one, I'm sure I'll have other challenges as well The more linux coders we can get in general, the better we are.

OOH OOOH *raises hand* I know what's up with the snow! it's wintery and holidayey!

The story so far... http://almiteycow.homeip.net/pub/apexdclinux.tar.bz2 (Double-posted so I get the new message flag, will edit into top post later)

http://www-128.ibm.com/developerworks/eser...2linux-sem.html Looks like it'll fix these errors in DownloadManager.cpp: I don't know enough C++ to understand what's going on, but I'll give it a try. If anyone can take a closer look, it'll be a big help. Basically, it looks like the RevConnect (or wherever it's from, but that's where it seems to be) code isn't so... portable. I'm going to post up what I've got for source sometime soon, and start a contest. Whoever can port that RevConnect code first gets $50

Progress: 27 files out of ~134 Working on SSL right now, in the CryptoManager.cpp file. YASSL? may be a problem. Tomorrow, I'll see if I can find a place on the web to drop my source, so others can take a crack at certain things. Gave up on working on porting Apex features to LDCPP. Porting Apex straight to Linux, fixing build errors and removing windows code when necessary. Things to check out before final release: Major: I don't know of an ADC hub for testing, need someone to find one and test for me. Minor: PG support has been removed. It will need to be readded. Removed memcpy_amd, it doesn't like linux too much. This could cause problems later though. EDIT: Removed webserver, will need to be readded. Morale: Higher than the crow's nest, yarr! :)

Gotcha, easy fix. StringDefs.h seems to be StringDefs.h still. Basically the difference between the linux c++ code and windows c++ code, is that all that stuff that just tosses warnings in windows, causes errors in linux. Or at least it seems that way.

Pending a Linux area for me to type this in.... Gotta keep notes for myself or my head might explode. Progress: 5 files out of ~134 Things to check out before final release: Major: I don't know of an ADC hub for testing, need someone to find one and test for me. Minor: AdcHub.cpp has some *ahem* interesting stuff going on at the bottom of it. Code may work, may not. If someone wants to take a look at it, I'll post the source. Figure out what's up with the names of the "Maximum & minimum file sizes (in bytes)." area of ADLSearch.h I can't get it to match Apex's code. Kibibytes are fine for now... but they bother me so. Here's my error: Morale: Well as it'll be. The crew be singin' bawdy songs whilst they be workin' and the first mate be wantin' to swab the deck. Arr, mateys! :blushing:

If it's a hub you have in your favorites list, you may want to try changing your nick there (right click, edit or properties or whatever).