On 23 December 2013 07:46, Russel Winder <russel@winder.org.uk> wrote:
> I am guessing I will need to raise issues in the various issue trackers but:
>
> I am finding that GtkD highlights some issues for GDC and LDC2. One of the moment relates to gtk.Builder.connectSignals. My code compiles and runs as expected with DMD, but with GDC and LDC2 the signals fail to connect.
>
> Also interesting to note that -o- appears to do bizarre things with both DMD and LDC2 (not an issue for GDC of course).
>

Thanks for the heads up.  I expect full bug report and a reduced by dustmite reproducible test case. ;-)

On Mon, 2013-12-23 at 08:15 +0000, Iain Buclaw wrote:
[…]
> Thanks for the heads up.  I expect full bug report and a reduced by dustmite reproducible test case. ;-)

It might not be that small given that you have to have a Glade file and a main, but I will ty.

Which issue tracker to submit to?
-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On 23 December 2013 08:34, Russel Winder <russel@winder.org.uk> wrote:
> On Mon, 2013-12-23 at 08:15 +0000, Iain Buclaw wrote:
> […]
>> Thanks for the heads up.  I expect full bug report and a reduced by dustmite reproducible test case. ;-)
>
> It might not be that small given that you have to have a Glade file and a main, but I will ty.
>
> Which issue tracker to submit to?
> --
> Russel.


For GDC, goto bugzilla.gdcproject.org;

On Monday, 23 December 2013 at 10:47:11 UTC, Iain Buclaw wrote:
> For GDC, goto bugzilla.gdcproject.org;

And for LDC, it's https://github.com/ldc-developers/ldc/issues, but I tink you know that URL already.

David

Hmm... I don't expect lots of magic there. It probably uses dlsym to find handlers, so they should be exported from the executable. Check if it's the case.