Tweaked Win32 bmk

BlitzMax Forums/BlitzMax Module Tweaks/Tweaked Win32 bmk

Brucey

(Posted 2007) [#1]

This is the source and binary of my tweaked bmk that allows you to link to libraries that are located out of the BlitzMax folder structure.

For example, if you have a file libQtGui4.a located in C:\Qt\4.2.2\lib you could now use :

Import "-LC:/Qt/4.2.2/lib"
Import "-lQtGui4"

... in your win32 build.
This makes it work like the Linux version of bmk.

You can download it from HERE.

Remember to backup your bmk.exe before using a different one - just in case

:-)

Chris C

(Posted 2007) [#2]

import "-DSOME_DUMB_C++_DEFINE"
import "somedumbcppcode.cpp"

how practical would somthing like this be? (would be quite handy) not to mention.....

import "-I/on/a/path/far/far/away"
import "c_file_needing_h_miles_away.cpp"

marksibly

(Posted 2007) [#3]

Hi,

import "-DSOME_DUMB_C++_DEFINE"

C compiler directives are a bit tricky - should they be 'local' to module code or should they be 'global' to the app?

import "-I/on/a/path/far/far/away"

This you can do that already with: Import "/on/a/path/far/far/away/*.h"

Brucey

(Posted 2007) [#4]

should they be 'local' to module code or should they be 'global' to the app?

I can see where both cases would be useful, though perhaps the easiest to implement would be to make it global to the app.

Wouldn't it be the case anyway that if you provide the import "-D..." in the module, it would only be relevant for the module build ?
And by using it in your App, since the module was already compiled it would only make a difference to the code you were compiling in the app?

Chris C

(Posted 2007) [#5]

C compiler directives are a bit tricky - should they be 'local' to module code or should they be 'global' to the app?

I'd say local to the following imports in that bmx file whether its a module or not is irrelevant

This you can do that already with: Import "/on/a/path/far/far/away/*.h"

this often doesn't work

in a C file with #import <foo/bah.h>
where foo is in /blah

import "/blah/foo/*.h"
doesnt allow the C file to compile

Brucey

(Posted 2007) [#6]

in a C file with #import <foo/bah.h>
where foo is in /blah

import "/blah/foo/*.h"
doesnt allow the C file to compile

What I do here usually, is :

Import "blah/*.h"
Import "blah/foo/*.h"

Which usually covers issues of files in foo reference headers without the foo/ part.

Chris C

(Posted 2007) [#7]

yeah, just seems a bit klunky thats all, full usage of gcc switches per bmx (and the files it imports) would be much more powerful and flexible