Re: How would I know if appvayer is parsing my yaml file?
On Tuesday, 16 July 2019 at 22:24:32 UTC, Mike Brockus wrote: If you never seen Meson before then set down and take a look: 樂 https://mesonbuild.com/ Quick question. I started integrating ci/cd best practices to my Meson projects and I was wondering how would I know if AppVayer is parsing my yaml file? I know I got a failed build because it was set to MSBuild by default. But after I set the value to script, how would I know it's doing its work and not just spinning it wheels. Reference. Sorry forgot I had to put the full path. https://github.com/squidfarts/c-example.git
How would I know if appvayer is parsing my yaml file?
If you never seen Meson before then set down and take a look: 樂 https://mesonbuild.com/ Quick question. I started integrating ci/cd best practices to my Meson projects and I was wondering how would I know if AppVayer is parsing my yaml file? I know I got a failed build because it was set to MSBuild by default. But after I set the value to script, how would I know it's doing its work and not just spinning it wheels. Reference.
Re: Wrong vtable for COM interfaces that don't inherit IUnknown
On Tuesday, 16 July 2019 at 01:38:49 UTC, evilrat wrote: As you can see it is by design. IUnknown has different vtbl[] comparing to regular D classes/interfaces. If it works with declaring your own empty IUnknown use it, also you can try extern(C++) which does similar thing to vtable, it might even work! ... Oh and let me put this here... Have you seen this? It even has very simple xaudio example. https://code.dlang.org/packages/directx-d Yes, i found that after posting. Declaring your interface extern(C++) and the methods in the interface extern(Windows) seems to do the trick. I hoped there would be a more elegant solution than to annotate each interface, but oh well. Thanks anyway!
Re: How would I write a travis-ci file for a Meson Dlang project?
On Tuesday, 16 July 2019 at 15:07:11 UTC, Mike Brockus wrote: If you never seen Meson before then pick up a camera and take a picture: 樂 https://mesonbuild.com/ Hello, everyone. I started adding continues integration as part of my development cycle and I was wondering how would I write a '.travis.yml' file for a D language project using Meson build system. https://github.com/squidfarts/c-executable.git Hello, an example https://github.com/dlang-community/libdparse/blob/master/.travis.yml
Re: How would I write a travis-ci file for a Meson Dlang project?
On Tuesday, 16 July 2019 at 15:07:11 UTC, Mike Brockus wrote: If you never seen Meson before then pick up a camera and take a picture: 樂 https://mesonbuild.com/ Hello, everyone. I started adding continues integration as part of my development cycle and I was wondering how would I write a '.travis.yml' file for a D language project using Meson build system. https://github.com/squidfarts/c-executable.git Hi, Related to your question, I currently add Dub support to this Jenkins pipeline library: https://sap.github.io/jenkins-library/ It contains various steps affecting dub or build for Dub. It isn't finished at this point in time. I will make an announcement hopefully in the next weeks. Kind regards Andre
How would I write a travis-ci file for a Meson Dlang project?
If you never seen Meson before then pick up a camera and take a picture: 樂 https://mesonbuild.com/ Hello, everyone. I started adding continues integration as part of my development cycle and I was wondering how would I write a '.travis.yml' file for a D language project using Meson build system. https://github.com/squidfarts/c-executable.git
Re: OPTLINK : Warning 9: Unknown Option : OUT
On Tuesday, 16 July 2019 at 13:33:01 UTC, Anonymouse wrote: IRCParser.init.chantypes even has a default value of "#". IRCParser.init.client.server.chantypes.
Re: OPTLINK : Warning 9: Unknown Option : OUT
On Tuesday, 16 July 2019 at 11:20:49 UTC, Boris Carvajal wrote:
The debugger exposes a crash in memchr from C runtime.
In file messaging.d line 216 called from the unittest just below
if (emoteTarget.beginsWithOneOf(state.client.server.chantypes))
chantypes.ptr is null. However chantypes.length is 1 so you are
assigning something invalid to it.
grep -nr "chantypes = " kameloso/
shows this place as something to care about
kameloso/source/kameloso/irc/parsing.d:1983: chantypes =
value;
Again, thank you for your immense help!
This is weird, chantypes should refer to a slice of immutables (a
string). Simplified:
void onISUPPORT(ref IRCParser parser, ref string slice)
{
import std.algorithm.iteration : splitter;
foreach (string value; slice.splitter(' '))
{
// ...
parser.client.server.chantypes = value;
}
}
IRCParser.init.chantypes even has a default value of "#".
I get the same error even if I try to work around it with .idup.
The only thing that does seem to help is checking for .ptr !is
null at the unittest location you mention.
if (state.client.server.chantypes.ptr &&
emoteTarget.beginsWithOneOf(state.client.server.chantypes))
I started a dustmite process, with some luck it should produce
something smaller by tonight or tomorrow.
Re: OPTLINK : Warning 9: Unknown Option : OUT
On Tuesday, 16 July 2019 at 09:07:03 UTC, Anonymouse wrote: This works for the reduced test program but not for my whole project. If you wouldn't mind trying it: git clone https://github.com/zorael/kameloso.git && cd kameloso && dub test (Windows 10, dmd 2.087 with your sed substitution) I'll try dustmiting it later tonight. The debugger exposes a crash in memchr from C runtime. In file messaging.d line 216 called from the unittest just below if (emoteTarget.beginsWithOneOf(state.client.server.chantypes)) chantypes.ptr is null. However chantypes.length is 1 so you are assigning something invalid to it. grep -nr "chantypes = " kameloso/ shows this place as something to care about kameloso/source/kameloso/irc/parsing.d:1983: chantypes = value;
Blog Post #0053: MVC VI - ComboBox with Pixbufs
Carrying on with installment #6 of the MVC series, we see how to use images in a ComboBox. This is the last bit of peripheral stuff we'll need to know before tackling the TreeView and (later) the TreeStore. Here it is: https://gtkdcoding.com/2019/07/16/0053-mvc-vi-image-combobox.html
Re: OPTLINK : Warning 9: Unknown Option : OUT
On Monday, 15 July 2019 at 12:40:57 UTC, Boris Carvajal wrote: On Monday, 15 July 2019 at 11:48:13 UTC, Anonymouse wrote: I built it with: dub fetch digger dub run digger -- build "stable + druntime#2675" I have not touched any digger.ini. The only one I can find is digger.ini.sample. sc.ini and dub output at: https://pastebin.com/jPnh4yEA dub test was invoked with: dub test --compiler=C:/cygwin/home/zorael/work/result/bin/dmd.exe -v I seem to get the same errors from a Cygwin terminal as from a cmd one. I'll give you another option if you just need that fix. Patch your phobos64.lib in the original dmd install directory using cygwin and sed, just run this exact command on cygwin prompt, editing the path to your case: sed -bi 's/%zu): /%llu):/' /c/d/dmd2/windows/lib64/phobos64.lib you can patch the 32bit libs if you need them. Then just run dub without "--compiler=" option to use your original dmd. This works for the reduced test program but not for my whole project. If you wouldn't mind trying it: git clone https://github.com/zorael/kameloso.git && cd kameloso && dub test (Windows 10, dmd 2.087 with your sed substitution) I'll try dustmiting it later tonight.
