User forums > General (but related to Code::Blocks)

Support for adding custom files to the build system

<< < (2/3) > >>

TDragon:
This is really excellent! I have a project which, interestingly enough, uses Flex and Lemon to generate C sources; custom build commands almost work the way they should but not quite (for some reason the Flex command is always run regardless of whether the source file has changed). This should clear that up. Much appreciated.

XayC:
Thanks Biplab, it's compiling now :D

Regards, XayC

TDragon:
Almost what I need but not quite... :P
Flex is stupid about backslashes, so I can't use $file in the command line macro; and $file_basename is out since my sources are in a subfolder relative to the project file and that would only generate files in the same folder as the project file.

This isn't C::B's fault, though -- and it works fine for the Lemon sources. Nice work.

darthdespotism:
Don't know if it's related to this new feature (nice thing as I want to use flex & bison very soon in a project) but codeblocks crashes on Gnu/Linux (Ubuntu 7.04) when trying to access the advanced options. Removing ~/.codeblocks did not solve anything

Revision is 4486

Installed packages:

../libcodeblocks0_1.0svn{rev}_i386.deb
../codeblocks_1.0svn{rev}_i386.deb
../libwxsmithlib0_1.0svn{rev}_i386.deb
../codeblocks-contrib_1.0svn{rev}_i386.deb

Crash-Log is attached

EDIT://
Seems to be a more general issue. Codeblocks also crashes on opening a project. May be some problem with the Compiler-Plugin as C::B always promts the compiler-selection on startup. I submitted it as a bug, hope this is the right action

[attachment deleted by admin]

Jan van den Borst:
On my Vista C::B compiles fine with the new advance dialog . However the advance dialog needs some rework as the dropdown boxes are too small. (See screenshot)

Jan

[attachment deleted by admin]

Navigation

[0] Message Index

[#] Next page

[*] Previous page