Jump to page: 1 2
Thread overview
codeblocks (x86_64) and DMD2 (32 bit)?
Oct 07, 2010
Gour D.
Oct 07, 2010
Stanislav Blinov
Oct 08, 2010
Gour D.
Oct 08, 2010
Stanislav Blinov
Oct 08, 2010
Gour D.
Oct 11, 2010
Gour D.
Oct 11, 2010
Gour D.
Oct 11, 2010
Gour D.
October 07, 2010
Hello!

I see that Emacs' d-mode is usable, but since we evaluate D as potential programming language for our upcoming GUI desktop application project (we hope there will be something out of QtD), I find C:B very nice IDE when working with a team of developers and would like to give it a testdrive.

However, I use x86_64 Linux and suppose that with 32-bit DMD2, it cannot work smoothly, right?

Can you point me and/or share some info what can be done with C:B & DMD2?


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA
----------------------------------------------------------------


October 07, 2010
Gour D. wrote:
> Hello!
> 
> I see that Emacs' d-mode is usable, but since we evaluate D as
> potential programming language for our upcoming GUI desktop
> application project (we hope there will be something out of QtD), I
> find C:B very nice IDE when working with a team of developers and
> would like to give it a testdrive.
> 
> However, I use x86_64 Linux and suppose that with 32-bit DMD2, it
> cannot work smoothly, right?
> 
> Can you point me and/or share some info what can be done with C:B &
> DMD2?
> 
> 

Actually, it is perfectly fine, as far as project management/building goes. Alas, C::B's syntax highlighting/parsing is AFAIK hard-coded and C++-oriented, so you won't get much editing sugar with it, but all the rest (workspaces, projects, configurations, building...) will work fine as soon as you set it up right.

What I did to make it work for me is:

1) In Settings->Compiler and debugger copied existing "Digital Mars D Compiler" and made "... D2 Compiler" out of it.
2) Set up toolchain path and executable names
3) In Other Settings->Advanced options->Commands set up command line for compiling/linking the way DMD accepts
4) In Other Settings->Advanced options->Others set up appropriate compiler switches for search paths, library linking and so on.

At least on Linux, it works fine. On Windows, there may be some linker issues as OPTLINK accepts command line that is very different from dmd/gcc/ar.

If you can't figure it out, I can send my default.conf that has all the settings I made to make it work (on Linux).
October 08, 2010
On Thu, 07 Oct 2010 23:21:15 +0400
>>>>>> "Stanislav" == Stanislav Blinov wrote:

Stanislav> Actually, it is perfectly fine, as far as project
Stanislav> management/building goes. Alas, C::B's syntax
Stanislav> highlighting/parsing is AFAIK hard-coded and C++-oriented,
Stanislav> so you won't get much editing sugar with it, but all the
Stanislav> rest (workspaces, projects, configurations, building...)
Stanislav> will work fine as soon as you set it up right.

Good.

Stanislav> At least on Linux, it works fine. On Windows, there may be Stanislav> some linker issues as OPTLINK accepts command line that is Stanislav> very different from dmd/gcc/ar.

I created my 32bit chroot on Archlinux and it works fine for console app, but I've problem building "Hello world" from QtD (http://www.dsource.org/projects/qtd/wiki/BuildLinux) which builds fine in cli.

Stanislav> If you can't figure it out, I can send my default.conf that Stanislav> has all the settings I made to make it work (on Linux).

Do you maybe use QtD as well?

Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA
----------------------------------------------------------------


October 08, 2010
Gour D. wrote:
> On Thu, 07 Oct 2010 23:21:15 +0400
>>>>>>> "Stanislav" == Stanislav Blinov wrote:
> 
> Stanislav> Actually, it is perfectly fine, as far as project
> Stanislav> management/building goes. Alas, C::B's syntax
> Stanislav> highlighting/parsing is AFAIK hard-coded and C++-oriented,
> Stanislav> so you won't get much editing sugar with it, but all the
> Stanislav> rest (workspaces, projects, configurations, building...)
> Stanislav> will work fine as soon as you set it up right.
> 
> Good.
> 
> Stanislav> At least on Linux, it works fine. On Windows, there may be
> Stanislav> some linker issues as OPTLINK accepts command line that is
> Stanislav> very different from dmd/gcc/ar.
> 
> I created my 32bit chroot on Archlinux and it works fine for console
> app, 

I assume you've created chroot to avoid hassle of building 32bit apps on amd64? I never bothered. It's all about compiler command line, anyway. Though I use Debian, not Archlinux.

> but I've problem building "Hello world" from QtD
> (http://www.dsource.org/projects/qtd/wiki/BuildLinux) which builds
> fine in cli.
> 

What is, exactly, the problem? Compile errors or linker ones? If you got proper search paths and compiler flags in C::B settings, you should be fine. I can tell that from the command line presented on that page: C::B would give you something similar, though it will make a two step process, e.g. compile main.d then link the project.

And, what do you mean by cli?

> Stanislav> If you can't figure it out, I can send my default.conf that
> Stanislav> has all the settings I made to make it work (on Linux).
> 
> Do you maybe use QtD as well?
> 

No, I don't. I once gave it a try, but never had time to return to it :(
October 08, 2010
On Sat, 09 Oct 2010 01:42:34 +0400
>>>>>> "Stanislav" == <stanislav.blinov@gmail.com> wrote:

Stanislav> I assume you've created chroot to avoid hassle of building Stanislav> 32bit apps on amd64? I never bothered. It's all about Stanislav> compiler command line, anyway. Though I use Debian, not Stanislav> Archlinux.

I created chroot in order to be able to test QtD properly.

Stanislav> What is, exactly, the problem? Compile errors or linker Stanislav> ones? If you got proper search paths and compiler flags in Stanislav> C::B settings, you should be fine. I can tell that from the Stanislav> command line presented on that page: C::B would give you Stanislav> something similar, though it will make a two step process, Stanislav> e.g. compile main.d then link the project.

It was linker problem...somehow could not find phobos lib. Now I resolved it.

Stanislav> And, what do you mean by cli?

Command Line Interface.

Stanislav> No, I don't. I once gave it a try, but never had time to Stanislav> return to it :(

I had great hope it will become ready despite all the problems faced by devs.


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA
----------------------------------------------------------------


October 11, 2010
Gour D. wrote:
> I see that Emacs' d-mode is usable, but since we evaluate D as
> potential programming language for our upcoming GUI desktop
> application project (we hope there will be something out of QtD), I
> find C:B very nice IDE when working with a team of developers and
> would like to give it a testdrive.

When working with QtD, wouldn't it be better (in the long run)
to add D2 language support to the Qt Creator cross-platform IDE?

http://qt.nokia.com/products/developer-tools
http://qt.gitorious.org/qt-creator

--anders
October 11, 2010
On Mon, 11 Oct 2010 08:55:21 +0200
>>>>>> "Anders" == Anders F Björklund <afb@algonet.se> wrote:

Anders> When working with QtD, wouldn't it be better (in the long run) Anders> to add D2 language support to the Qt Creator cross-platform IDE?

It might be indeed...But, I'm not sure it would go upstream, iow, that Nokia would commit support to D.

otoh, Code:Blocks is open-source and there is,  I believe, better chance that it can become part of C:B.


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA
----------------------------------------------------------------


October 11, 2010
Gour D. wrote:
> Anders> When working with QtD, wouldn't it be better (in the long run)
> Anders> to add D2 language support to the Qt Creator cross-platform IDE?
> 
> It might be indeed...But, I'm not sure it would go upstream, iow, that
> Nokia would commit support to D.

So patch it ? (LGPL)

> otoh, Code:Blocks is open-source and there is,  I believe, better
> chance that it can become part of C:B.

Sorry, what can become part of Code::Blocks ? Qt ? D2 ?

--anders
October 11, 2010
On Mon, 11 Oct 2010 12:00:50 +0200
>>>>>> "Anders" == Anders F Björklund <afb@algonet.se> wrote:
Anders> So patch it ? (LGPL)

It's a pain to maintain it then.

Anders> Sorry, what can become part of Code::Blocks ? Qt ? D2 ?

Support for QtD, iow. using QtDesigner within C:B.


Sincerely,
Gour

-- 

Gour  | Hlapicina, Croatia  | GPG key: CDBF17CA
----------------------------------------------------------------


October 11, 2010
Gour D. wrote:

> Anders> So patch it ? (LGPL)
> 
> It's a pain to maintain it then.

Just a thought... Looked like it had a plugin structure ?

i.e. "src/plugins/cppeditor" and "src/plugins/cpptools"

But it would need things like a front-end for completion.

So while you are recruiting new QtD maintainers anyway... :-)


> Anders> Sorry, what can become part of Code::Blocks ? Qt ? D2 ?
> 
> Support for QtD, iow. using QtDesigner within C:B.

There is some support for GTK+ and Qt4 project templates.

Just that it seemed to make more sense to support wxD...
(adding D support to the wxWidgets template, and wxSmith)

Not sure what is needed for QtDesigner, opening the .ui ?


If you want to see more support for QtD or D2 in C::B,
you should post that to http://forums.codeblocks.org/

It needs new developers to add *real* support for the D
languages, other than implementing as C++ compilers...


Otherwise it will be left with wxD and D1 (GDC/LDC/DMD).

See http://forums.codeblocks.org/index.php/topic,12246.0.html

--anders
« First   ‹ Prev
1 2