Blog Topic Suggestion Box

While I’ve been managing this Blog for some time (and the previous two as well), I’ve had little to no requests for post-topics.

While my e-mail, and Todd’s, and arne’s, and… is shown here and in other places, I guess people are hesitant to send a mail.

So, feel free to post here in this post if you want me or anyone else to talk about a certain topic. Or explain a certain feature. Or explain a particular bug. Or…

Please note that it’s very difficult for us to answer questions about a particular modification of DC++ or even a different client. (To increase the chances of us talking about a feature in another mod/client, have the feature/question be generalized.)

(Of course, browse the blog or FAQ first. Your topic may have already been discussed.)

Please add further comments here.

Updating current and old posts

There is a particular thing I don’t like when it involves certain posts.

Like the previous Credit post or the TTH-Version post.

When I’m writing a post here, I’m essentially setting what I say to stone. And that is something I want to avoid, particularly if it involve things that are prone to change. Like who is credited or what the new TTH of a version is.

So, to improve the (*joke*) gigantic interactivity (/*joke*) here, I would appreciate if people would drop a comment in the following posts when things change.

Credits
TTHversion
Different ADC clients

Thanks all.

(If you notice some other post that require the same attention, feel free to post.)

Credits

After creating a feature or fixing a bug, and the patch is included in DC++, arne (usually) add your name or pseudonym to the changelog (“thanks yourname”). If you haven’t contributed patches before, he also add your name/pseudonym to DC++’s About Box. Since I don’t think these people and projects are getting deserved credit for everything, here’s that list of people and projects that have contributed to DC++;

DC++ uses libzip2, thanks to Julian R Steward and team for providing it.
DC++
uses STLPort (www.stlport.org), a most excellent STL package.
DC++ also utilize zlib.
DC++
 includes GeoIP data created by MaxMind, available from http://maxmind.com/.
DC++ uses yassl from
www.yassl.com, thanks to Todd Ouska and Larry Stefonic.

People:
 per lindén, martin skogevall,
geoff, carxor, luca rota, dan kline, mike, anton, zc, sarf, farcry, kyrre aalerud,

 opera, patbateman, xeroc, fusbar, vladimir marko, kenneth skovhede, ondrea, todd pederzani, who, sedulus,

 sandos,henrik engström, dwomac, robert777, saurod, atomicjo, bzbetty, orkblutt, distiller, citruz, dan fulger,  

 cologic, christer palm, twink, ilkka sepp�l�, johnny, ciber, theparanoidone, gadget, naga, tremor,

 joakim tosteberg, pofis, psf8500, lauris ievins, defr, ullner, fleetcommand, liny, xan, olle svensson,

 mark gillespie, jeremy huddleston, bsod, sulan, jonathan stone, tim burton, izzzo, guitarm, paka,

 nils maier, jens oknelid, yoji, krzysztof tyszecki, poison, pothead, pur, bigmuscle, martin, jove,

 bart vullings, steven sheehy, tobias nygren.

(It’s a mere copy of the About Box.) (“People” is in chronological order of when the patch was added to DC++.) (You can find me somewhere in there.)

 

Help the file!

Since I’ve been posting a bunch of “how to compile this and that” posts lately, I am going to do that today as well.

And this time, with DC++’s help file.

It’s an easy task, requiring basically only one program from Microsoft; HTML Help Workshop.

Download HTML Help Workshop and install it in C:/Program Files. (Or wherever the %ProgramFiles% system variable point to.)

Now go in the help/ directory in DC++’s source and run compile.cmd. This will automatically generate a new ‘version’ of the changelog in the helpfile, and (temporarily) copy res/users.bmp so one of the FAQs can take advantage of it. The help file will now appear in app/ (extension .chm).
If you want to change the language of the help file, feel free to do that. It’s just to open the .html files in an editor and change the text. (Remember? It’s HTML Help Workshop.)

If you want to add or remove a file from the help file;

  1.   Open toc.hhc in a text editor and add the file in an appropriate LI/object-tag.
  2. Open help.vcproj in a text editor and add the file in an appropriate File-tag.
  3. Open DCPlusPlus.hhp in a text editor and add the file in the [FILES] part. If you want it to have an alias, and be “call-able” from DC++, add it as well under the [ALIAS] part.
  4. Modify index.html (or whatever other file you want to point to your new file).
  5. Run compile.cmd.

If you want to upload it so others can take advantage of your change, feel free to upload it to the Language tracker.
Something many may not know about, is that the help file require one other program to be viewable. It is Internet Explorer. Yes. So, while the .chm is initially constructed by platform independent HTML files, the end help file is not.

And they keep coming

DC++ 0.697 is now out. Nothing special, just a few fixes. The nick-bug is fixed though.

0.11 of ADC is released!

Version 0.12 of the ADC protocol is now released. An .odt is also available if you want that… A summary of what has been changed (arne’s words); Differences are few and far between; D type messages replaced by E (as in echo), the new D type does not have to be echoed back to the originator; some new INF field; Added BZIP as extension for files.xml.bz2
Here’s a diff if you want to see exactly was has changed.

(I know that this Blog entry’s title is incorrect.)

Compiling DC++ with Visual Studio 2003

This guide is about compiling DC++ on Windows, with Visual studio 2003.

To compile DC++, you will need a few things.

First, download the DC++ source, and unpack it in C:\dcplusplus\dcplusplus696\. (So you got C:\dcplusplus\dcplusplus696\windows, C:\dcplusplus\dcplusplus696\client etc.)

Download STLport, and unpack it in C:\dcplusplus\STL so you got C:\dcplusplus\STL\config etc.

Download WTL and unpack it in C:\dcplusplus\WTL so you got C:\dcplusplus\WTL\include etc.

Download the latest SDK, or get the natupnp.h file from Bugzilla. Place it in C:\dcplusplus\natupnp\. (I think I have it in some Visual Studio include path, but this should work fine too.)

Download YaSSL and unpack it in C:\dcplusplus\YaSSL so you got C:\dcplusplus\YaSSL\certs etc.

Download Python and install it. (I got mine in the default folder)

Enter C:\dcplusplus\dcplusplus696\. Open up DCPlusPlus.rc and change the line #include “wtl\\atlres.h” to #include “atlres.h”

Open up the workspace (DCPlusPlus.sln)

Under the Tools menu, press Options.

Go to Projects and then VC++ Directories.

Under ‘Show directories for’ select ‘Include files’.

Add the STL folder, WTL\include folder, YaSSL folder and then the natupnp folder. (They should be in the top.)

Under the Build menu, press Build solution and Visual Studio should compile you an executable that is located in C:\dcplusplus\dcplusplus696\app\.

To change Python path, go to client->Header Files->StringDefs.h->Properties->Custom build step and change the appropriate values.

TTH is the standard

A new version of DC++ is out; 0.696. It is a… quite aggressive version. It now require that all files have a TTH. No files without TTH is shown in the search and you aren’t able to download any file that doesn’t have a TTH. TTH is the standard now and all is great.

Compiling ADCH++ with Mingw on Windows

And another how-to on compiling ADCH++. This time with Mingw on Windows. Check out the previous POSIX and Visual Studio 2005 (Windows) tutorials.

Credit for this tutorial goes to Pothead.

  1. Install Python
  2. Install scons
  3. Install swig
  4. Install boost (copy the contents of boost_1_33_1\boost to C:\Boost\include\boost-1_33_1\boost )
  5. Install mingw (not sure what parts are needed, but i got the gcc-core gcc-g++ binutils runtime utilities and w32api, and it works with all of them)
  6. Install Msys (part of mingw)
  7. Download and place Stlport 5.0.2 in the STLPort directory in Adchpp’s root directory
  8. Ensure Pyton, Swig and Mingw’s paths are available in %PATH%
  9. Compile STLPort
    1. Load up Msys
    2. Navigate to the STLPort\build\lib directory
    3. Type: make -f gcc.mak depend
    4. Type: make -f gcc.mak install
    5. Close Msys
  10. Compile Adchpp
    1. Goto adchpp directory
    2. To build in debug mode Type: scons to build in debug mode
    3. To build in release mode Type: scons mode=release

(To find links to the other programs, look in the previous posts or use a search engine.)

Compiling ADCH++ on POSIX

This is a how-to to compile ADCH++ on POSIX, specifically Linux Ubuntu 6.06 LTS. If you are on Windows, check out the previous post.

An early disclaimer; I am not a experienced POSIX user, and I’m certainly no expert at compiling ADCH++, but it’ll have to do.

The following libraries/commands are what I experienced I had to do when trying to compile ADCH++.

Create the directory ~/adch++/. (Or wherever/whatever you want to call it.)

Enter the directory, and download ADCH++ by doing “svn checkout https://svn.sourceforge.net/svnroot/adchpp/ –username anonymous”

Download the following; Boost 1.33.1, swig 1.3.29, STLport.
Download and install bjam (I used 3.1.11-1 and downloaded it through Synaptic.)

Extract STLport in ~/adch++/, so you have ~/adch++/STLport/. Enter ~/adch++/STLport/build/lib and do ./configure, then do “make -f gcc.mak depend” and then “make -f gcc.mak install”.

Extract boost_1_33_1 so you have ~/adch++/boost_1_33_1/. Do ./configure, then “make” and then “make install”.

Extract swig anywhere, enter the directory it is in. Do ./configure, then “make” and then “make install”.
Enter ~/adch++/, and do “scons”.

Now, I should say that I encountered two problems. You may not experience them. Firstly; the variable ‘versionString’ was apparently unreachable, so I just removed it and put any string in quotes. So, s/versionString/”ADCH++”. Secondly; the variable ‘FULLVERSIONSTRING’ was also apparently unreachable, so I just removed it and put any string in quotes. So, s/FULLVERSIONSTRING/”ADCH++”.

Doing just “scons” will produce ADCH++ in ‘debug’ mode. If you want it in ‘release’ mode, do “scons mode=release”. (You can ofcourse specify ‘debug’ the same way.)

When scons is complete, enter ~/adch++/build. You will see either the debug or release directory (or both). Enter now ~/adch++/build/debug-default/bin/. And now do “./adchpp”. You should now have a working ADCH++!

The default port is 2780, but you can change that in ~/adch++/etc/. Open adchpp.xml and scroll down to the port, and enter whatever you want. (Remember, there is no default port in ADC.)

If you know something that isn’t necessary, please do tell. If you encounter any problems, I’d prefer the ADCH++ forum.

Design a site like this with WordPress.com
Get started