Re: DUB 0.9.21 beta 1
On 2013-12-02 10:10, Sönke Ludwig wrote: Using "dub test --main-file=...". See also "dub test --help". * Can this be specified in the package.json file so invoking "dub test" will always use a custom main file? * Don't know how it works now but it would be nice if dub could pass all remaining command line arguments to the custom main function -- /Jacob Carlborg
Re: LDC 0.12.1 has been released
On Tuesday, 3 December 2013 at 09:00:25 UTC, Rory McGuire wrote: Nice. Any chance that the packages are able to have a similar layout to dmd? It is easy to just rearrange the files to match DMD's directory structure, you just have to update ldc2.conf accordingly. However, as we don't ship one big archive for all possible operating systems (including the source code) like DMD does, but binary-only packages for each OS, I think adopting the DMD zip directory structure would only be confusing. The current layout is supposed to make it as easy as possible to just extract the archive somewhere and immediately be able to use the compiler (I use /opt/ldc… for keeping the different releases around, but you could also extract the files to /usr/local directly). But I believe what you were asking for is a layout to match the DMD .deb packages? In this case, this would be a a job for the person providing LDC Debian packages, which we – unfortunately – currently don't have at all. Since LDC is Free Software in the Debian sense, it should even be possible to include it in the official repositories (again). There were a few discussions in that direction, but I don't think anything concrete resulted from that yet. Please contact us if you would be able to help with this! David
Re: DUB 0.9.20
Am 03.12.2013 13:47, schrieb Bruno Medeiros: > On 29/11/2013 17:01, Sönke Ludwig wrote: >> A fresh DUB release is out. Apart from the usual bug fixes, there are a >> few considerable changes: >> > > Quick question: is there a way to install/fetch the dependencies of a > package, without having to build? That is, without using "dub build" ? > > "dub upgrade" should be the right call. Possibly with "--root=path/to/package" or "dub upgrade pkgname:subpkgname --root=path/to/package".
Re: vibe.d 0.7.18 has been released
On 2013-12-03 09:37:07 +, Atila Neves said: I wrote an MQTT broker on top of vibe.d's TCP functionality: https://github.com/atilaneves/mqtt Hi, thanks & cool stuff. Since I'm still a big fan of the BEEP protocol (framework for application protocols), I'm wondering if we could use vibe.d as a base and make a BEEP implementaiton. Having one out-of-the-box in D would be a "killer" as it reduces the effort to write network applications tremendously. -- Robert M. Münch Saphirion AG http://www.saphirion.com smarter | better | faster
Re: DUB 0.9.20
On Tuesday, 3 December 2013 at 13:00:06 UTC, Mike Parker wrote: On 12/3/2013 9:47 PM, Bruno Medeiros wrote: On 29/11/2013 17:01, Sönke Ludwig wrote: A fresh DUB release is out. Apart from the usual bug fixes, there are a few considerable changes: Quick question: is there a way to install/fetch the dependencies of a package, without having to build? That is, without using "dub build" ? dub install packageName It is `dub fetch` now, to remove common confusion. Alias to old name is preserved but undocumented.
Re: DUB 0.9.20
You can make dub aware of such a package with: $ dub all-local . ~master In which case, this particular package doesn't need to be dub-installed. I meant "add-local" not "all-local".
Re: DUB 0.9.20
On Tuesday, 3 December 2013 at 13:18:13 UTC, Bruno Medeiros wrote: That only works if packageName is a package in the DUB registry. It won't work for a locally created package. You can make dub aware of such a package with: $ dub all-local . ~master In which case, this particular package doesn't need to be dub-installed.
Re: DUB 0.9.20
On 03/12/2013 13:00, Mike Parker wrote: On 12/3/2013 9:47 PM, Bruno Medeiros wrote: On 29/11/2013 17:01, Sönke Ludwig wrote: A fresh DUB release is out. Apart from the usual bug fixes, there are a few considerable changes: Quick question: is there a way to install/fetch the dependencies of a package, without having to build? That is, without using "dub build" ? dub install packageName That only works if packageName is a package in the DUB registry. It won't work for a locally created package. -- Bruno Medeiros - Software Engineer
Re: DUB 0.9.20
On 12/3/2013 9:47 PM, Bruno Medeiros wrote: On 29/11/2013 17:01, Sönke Ludwig wrote: A fresh DUB release is out. Apart from the usual bug fixes, there are a few considerable changes: Quick question: is there a way to install/fetch the dependencies of a package, without having to build? That is, without using "dub build" ? dub install packageName
Re: DUB 0.9.20
On 29/11/2013 17:01, Sönke Ludwig wrote: A fresh DUB release is out. Apart from the usual bug fixes, there are a few considerable changes: Quick question: is there a way to install/fetch the dependencies of a package, without having to build? That is, without using "dub build" ? -- Bruno Medeiros - Software Engineer
Re: DUB 0.9.21 beta 1
Am 03.12.2013 10:34, schrieb Atila Neves: >> It also supports setting a custom file containing main(), so that for >> example custom unit test runners can be specified and similar > > > Awesome! > >> things. In >> this case, the generated file looks like this: >> --- >> module test_main; >> import ; >> import ; >> --- >> >> For packages with only executable configurations it behaves the same as >> "dub run --build=unittest". > > So custom_main_module defines the main function to be executed? > Exactly. main() will usually be empty, as unit tests by default run before main() is called, but it can be used to disable the standard Runtime.moduleUnitTester and do something customized.
Re: LDC 0.12.1 has been released
Hi Rory! On Tuesday, 3 December 2013 at 09:00:25 UTC, Rory McGuire wrote: Nice. Any chance that the packages are able to have a similar layout to dmd? The binary packages follow the simple pattern that you can extract them into /opt, add the path to the bin folder and start using LDC. The important piece of information is etc/ldc2.conf. You can rearrange even the binary package as you want as long as you keep ldc2.conf in sync. So, yes, the packages can be arranged in a similar layout to dmd. A simple shell script should be able to do this. Regards, Kai
Re: vibe.d 0.7.18 has been released
On Friday, 29 November 2013 at 17:31:41 UTC, Robert M. Münch wrote: On 2013-11-26 19:31:44 +, Sönke Ludwig said: Homepage: http://vibed.org/ DUB package: http://code.dlang.org/packages/vibe-d GitHub: https://github.com/rejectedsoftware/vibe.d Out of curiosity, it looks like vibe.d could be used to implement all kind of network protocolls. Is that right? Or is this use-case to screwed-up for it? I wrote an MQTT broker on top of vibe.d's TCP functionality: https://github.com/atilaneves/mqtt
Re: DUB 0.9.21 beta 1
It also supports setting a custom file containing main(), so that for example custom unit test runners can be specified and similar Awesome! things. In this case, the generated file looks like this: --- module test_main; import ; import ; --- For packages with only executable configurations it behaves the same as "dub run --build=unittest". So custom_main_module defines the main function to be executed?
Re: LDC 0.12.1 has been released
On Mon, Dec 2, 2013 at 9:02 AM, Kai Nacke wrote: > Hi everyone, > > LDC 0.12.1, the LLVM-based D compiler, is available for download! > This is a bug-fix only release. It is built on the 2.063.2 frontend and > standard library and supports LLVM 3.1-3.3 (OS X: 3.2 only). > > As usual, you can find links to the changelog and the binary packages over > at digitalmars.D.ldc: > http://forum.dlang.org/post/fmhdagtwppcpkajgr...@forum.dlang.org > > Regards, > Kai > Nice. Any chance that the packages are able to have a similar layout to dmd? I use this command line to add each dmd as an alternative in Ubuntu would be nice to add ldc as an option. update-alternatives --install /usr/bin/dmd dmd /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/dmd 2 --slave /usr/bin/rdmd rdmd /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/rdmd --slave /usr/bin/dman dman /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/dman --slave /usr/bin/ddemangle ddemangle /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/ddemangle --slave /usr/bin/dumpobj dumpobj /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/dumpobj --slave /usr/bin/obj2asm obj2asm /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/obj2asm --slave /etc/dmd.conf dmd.conf /usr/lib/dmd/dmd-2063/dmd2/linux/bin64/dmd.conf --slave /usr/include/d/phobos phobos /usr/lib/dmd/dmd-2063/dmd2/src/phobos --slave /usr/include/d/druntime druntime /usr/lib/dmd/dmd-2063/dmd2/src/druntime --slave /usr/lib/x86_64-linux-gnu/libphobos2.so libphobos2 /usr/lib/dmd/dmd-2063/dmd2/linux/lib64/libphobos2.so --slave /usr/lib/i386-linux-gnu/libphobos2.so libphobos2-i386.so /usr/lib/dmd/dmd-2063/dmd2/linux/lib32/libphobos2.so --slave /usr/lib/x86_64-linux-gnu/libphobos2.a libphobos2.a /usr/lib/dmd/dmd-2063/dmd2/linux/lib64/libphobos2.a --slave /usr/lib/i386-linux-gnu/libphobos2.a libphobos2-i386.a /usr/lib/dmd/dmd-2063/dmd2/linux/lib32/libphobos2.a
