Code::Blocks

User forums => Using Code::Blocks => Topic started by: nrgyzer on January 09, 2011, 02:51:34 pm

Title: xfbuild (DMD) and import-paths in CB
Post by: nrgyzer on January 09, 2011, 02:51:34 pm
Hey guys,

I installed CodeBlocks on linux and it works great with the default Digital Mars D Compiler settings. But... it seems that CodeBlocks always ignore my import paths. I changed the default dmd compiler executable to xfbuild (which includes and compiles all which have anything to do with the project), thus that imported projects/files or modules are automatically compiled.

When I add a directory like /home/user/Desktop/MyProjectToImport to the folder paths (in Settings > Compiler and debugger > Search directories > Compiler), CodeBlocks does not apply the path to the compiler. I always get a "undefined reference to"-error which means that the compiler can't find symbols which are defined in other (imported) projects. Does anyone know what I'm doing wrong?


Thanks in advance!
Title: Re: xfbuild (DMD) and import-paths in CB
Post by: oBFusCATed on January 09, 2011, 03:38:55 pm
Read this: http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F'

p.s. you've posted to the wrong subforum, this one is for development of C::B, not for using C::B to develop your app...
Title: Re: xfbuild (DMD) and import-paths in CB
Post by: MortenMacFly on January 09, 2011, 03:40:15 pm
It's not enough to set the "import paths" to the other projects (libraries) to use, but you also need to link against the libraries that actually provide the symbols.

BTW: I am not sure what you mean by "import paths" btw. - I only know "include paths" fr the compiler / linker.
Title: Re: xfbuild (DMD) and import-paths in CB
Post by: oBFusCATed on January 09, 2011, 04:05:40 pm
In D import is something like include in C/CPP
Title: Re: xfbuild (DMD) and import-paths in CB
Post by: nrgyzer on January 15, 2011, 05:13:16 pm
Thanks for reply... http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F solved the problem :).