Martijn van Iersel:
> You can jump between compiler error messages with F4 - I use this
> feature a lot. However, if the error is in a file in a different
> directory, and the file is specified by a relative path, that file is
> not opened and instead SciTE goes to the corresponding line in the
> active file.
SciTE tries a bunch of places using the relative path. It tries
1) The directory of the current file when the command was executed
2) The directory in which the command was executed
3) The directory of the current file when the F4 key is pressed
4) As an absolute path
5) All the buffers to find one with the same name
> For example, when I run make, I get output like this:
> >mingw32-make -Cd:\prg\project
SciTE has no idea that you are setting a particular directory using
a command line argument.
> mingw32-make: Entering directory `d:/prg/project'
It doesn't see this either.
> g++ -Iinclude -O3 -Wall -s -MMD -c src/monster.cpp -o obj/mingw/monster.o
> src/monster.cpp: In member function `virtual void Monster::update()':
> src/monster.cpp:128: error: expected `,' or `;' before `{' token
> src/monster.cpp:146: error: expected `}' at end of input
> But SciTE won't open monster.cpp when I press F4.
>
> So my question is: Is there a way to tell SciTE where to search for the
> source files, or any other way to solve this issue without having to
> change the directory layout of my projects?
There is no way to set a search path but you can ask for build to
run from a particular directory with
command.build.directory.<filepatttern>
For example, in the scite/src directory, the local.properties file has
command.build.directory.*.cxx=..\win32
command.build.directory.*.h=..\win32
Neil
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
