@Muttley: Imports and includes have relative paths to the main bmx file of every project, when they're in the same tree structure. Place the bls file in the same folder as the main bmx file of your solution, and it should work out of the box. But anyway, I would like to have more information about how's your solution organized on the disk (folders structure and the like). I supose you can not send me a copy of your solution, but if you could, that would be very helpful.
To sort out this properly, place any import in a subfolder of the 'importer' bmx file (that will activate the relative path on this import, if I'm not wrong). In the solution file bls, there are still not-relative paths, and this is something I'm not sure I'll be changing as BlitzMax can by design spread files all over your disk, that's specially happening when dealing with regular code + modules. If you have any suggestion how could this be improved, I'll be happy to read it :D
this is a screenshot of the properties window of a game I'm working on:
As you can see, all the files are relative, so I have no problems moving the solution from one computer to another, they're just placed in the same base-tree structure.
To sort out this properly, place any import in a subfolder of the 'importer' bmx file (that will activate the relative path on this import, if I'm not wrong). In the solution file bls, there are still not-relative paths, and this is something I'm not sure I'll be changing as BlitzMax can by design spread files all over your disk, that's specially happening when dealing with regular code + modules. If you have any suggestion how could this be improved, I'll be happy to read it :D
this is a screenshot of the properties window of a game I'm working on:
As you can see, all the files are relative, so I have no problems moving the solution from one computer to another, they're just placed in the same base-tree structure.