Thread overview
GDC missing betterC switch
July 18
Hello, I am looking for help using betterC with GDC
(after this, my next step was to see if I can use wxWigdets with GDC betterC without
 wxD wrappers)

This question is essentially same as below from 2018( it did not have any answers).
https://forum.dlang.org/thread/usdqpbusosanlsugwbip@forum.dlang.org

If anyone would help with guidance on the above, very much appreciated.




July 18
On Thursday, 18 July 2019 at 14:29:36 UTC, vladislavp wrote:
> Hello, I am looking for help using betterC with GDC
> (after this, my next step was to see if I can use wxWigdets with GDC betterC without
>  wxD wrappers)
>
> This question is essentially same as below from 2018( it did not have any answers).
> https://forum.dlang.org/thread/usdqpbusosanlsugwbip@forum.dlang.org
>
> If anyone would help with guidance on the above, very much appreciated.

Iain:

`-fexceptions`, `-frtti`, and `-fmoduleinfo` control individual implicit Exception, TypeInfo, and ModuleInfo code generation, and `-nophoboslib` tells the driver to no bother attempting to link a phobos library.
All are wrapped together in a `-fdruntime` convenience switch, to which `-fno-druntime` turns off all of the above.

You can get away with:

module object;
extern(C) int main() { return 0; }

As a minimal program and it will just compile, no fancy switches required.
gcc test.d && ./a.out
July 18
On Thu, 18 Jul 2019 at 18:15, Eugene Wissner via D.gnu <d.gnu@puremagic.com> wrote:
>
> You can get away with:
>
> module object;
> extern(C) int main() { return 0; }
>
> As a minimal program and it will just compile, no fancy switches
> required.
> gcc test.d && ./a.out

Yes, that is using gcc to compile D code, and no that is not a typo. :-)

-- 
Iain
July 19
On Thursday, 18 July 2019 at 18:50:07 UTC, Iain Buclaw wrote:
> On Thu, 18 Jul 2019 at 18:15, Eugene Wissner via D.gnu <d.gnu@puremagic.com> wrote:
>>
>> You can get away with:
>>
>> module object;
>> extern(C) int main() { return 0; }
>>
>> As a minimal program and it will just compile, no fancy switches
>> required.
>> gcc test.d && ./a.out
>
> Yes, that is using gcc to compile D code, and no that is not a typo. :-)

Thank you Ian, Eugene.
I got it.