Request for a new port - toxcore

[lubodiakov@…]

Toxcore contains all the libraries on which Tox depends.

See: github.com/irungentoo/toxcore.

[lubodiakov@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Thanks. Some observations:

• Are you certain all of the dependencies you're listed are only build dependencies? None of them are used as libraries?
• The maintainers line must be you valid email address, in our obfuscated host:user format.
• I see you are using the github portgroup but are downloading from the git repository directly. Is there a reason why you cannot use the tarballs github will automatically generate? Take a look at the documentation in the comments in the github portgroup file​ for proper usage.
• You don't need to set the name since running github.setup sets it for you.

[lubodiakov@…]

Replying to ryandesign@…:

I think most (all?) of them are indeed used to build only. Toxcore builds only libraries for use by client apps, but no binaries by itself. I may be mistaken, not a programmer.

Missed that. Thanks.

No reason other than I got confused by the docs, and pieced this together from other Portfiles found online. I actually think it would be much more maintainable the way you suggest, so I'll rework it. Strike that, the project is under heavy development, there isn't even a version 1.0, no releases at all on github as far as I know.

Ok, I'll skip name then.

[ryandesign (Ryan Carsten Schmidt)]

There don't need to be releases on github to be able to use automatically-generated tarballs. Just try omitting the "fetch.type git" line, and add the checksums line with appropriate values.

[lubodiakov@…]

Replying to ryandesign@…:

I can omit the "fetch.type git" line, but I have no idea where to get the checksum with "the appropriate values". I don't see any option to download a tarball, and no checksums generated by github. I can generate rmd160 and sha256 sums myself if I download the file, but which file? The zip on the right side of the project page, or what? Other github hosted projects with releases have both a zip and a tarball in the releases page, but this project has no releases (yet) so where would the tarball be? I'm not finding it.

Trying to understand, but still not clear.

[ctreleaven (Craig Treleaven)]

Replying to lubodiakov@…:

Replying to ryandesign@…: I can omit the "fetch.type git" line, but I have no idea where to get the checksum with "the appropriate values". I don't see any option to download a tarball, and no checksums generated by github. I can generate rmd160 and sha256 sums myself if I download the file, but which file? The zip on the right side of the project page, or what? Other github hosted projects with releases have both a zip and a tarball in the releases page, but this project has no releases (yet) so where would the tarball be? I'm not finding it.

It is a feature of github that they will automatically create an archive of the project reflecting the state of the project as of the commit you specify in our github.setup line. If you run 'sudo port -d checksum' as you are developing the port (before adding the checksums), the output will include appropriately formatted checksum lines that you can copy/paste into your Portfile.

[lubodiakov@…]

Replying to ctreleaven@…:

Replying to lubodiakov@…:

Replying to ryandesign@…:

Thank you ctreleaven. I did not know that. I'll go try it right now.

Update: I think I got it. Uploading what is hopefully the final portfile until they update the commits again.

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

It appears to build OK on Mavericks; but I wonder if it is using the right compiler

clang: warning: argument unused during compilation: '-pthread'

[lubodiakov@…]

Replying to khindenburg@…:

It appears to build OK on Mavericks; but I wonder if it is using the right compiler

clang: warning: argument unused during compilation: '-pthread'

No idea. I build on Leopard (10.5) with gcc 4.x (from Xcode 3.1.4) and I did not notice any such warning. Also, other than the clang in Macports I have no Apple supplied clang to test anything. My main goal is that it should compile ok, even with some warning(s).

[mf2k (Frank Schima)]

As reporter, you do not need to Cc yourself.

[kurthindenburg (Kurt Hindenburg)]

I have a working version

Where did you get the version 0.5.2? Are there any clients that use this library working on OSX?

[lubodiakov@…]

Sorry for the delay, missed the email copy of this comment and had not logged in here for a while.

Replying to khindenburg@…:

I have a working version

Not sure how that relates?

Where did you get the version 0.5.2?

The versioning is a bit complicated and mixed up, not by my choice. I.e. it is that way in the upstream project. There is a build number for toxcore, it can be seen from the projects Jenkins server: ​https://jenkins.libtoxcore.so/job/Sync%20Tox/

As of now (Feb. 16, 2015 it is at build 500. This is the same build number I'm using in my newest portfiles for toxcore, which I'm attaching. There are separate version numbers (such as 0.5.2) which appear inside clients that use toxcore, such as toxic: ​https://github.com/Tox/toxic

Are there any clients that use this library working on OSX?

Yes I have built Toxic (CLI and audio, no video) myself, and others have built GUI clients on newer versions of OS X.

[lubodiakov@…]

Updated to Jenkins build 500, added options to build with 10.4u SDK

[barracuda156]

Can be closed with: ​https://ports.macports.org/port/toxcore/details