XIncludeFile and IncludeFile to search local directory first

[Mistrel]

I would like to see the XIncludeFile and IncludeFile functions search the directory local to the currently included file first before searching the directory local to the file passed to the compiler.

Trond provided a trick to do this by adding another line but I believe this behavior should be built into these functions. I see no tangible benefit to for these functions to search only the compile file directory.

http://www.purebasic.fr/english/viewtopic.php?p=268111
http://www.purebasic.fr/english/viewtopic.php?t=30504

[Little John]

+1

Regards, Little John

[PB]

I don't understand the request. I have files in the same folder as my source
and they're all included just fine like this:

Code: Select all

IncludeFile "Name.pb"

What am I misunderstanding?

[Mistrel]

IncludeFile and XIncludeFile only work with files relative to the main source file passed to the PB compiler (%COMPILEFILE).

All files should work like this by default and only if the file is not found check the directory relative to the main source file:

Code: Select all

IncludeFile(#PB_Compiler_File+"\..\"+"Include.pb")
XIncludeFile(#PB_Compiler_File+"\..\"+"Include.pb")

[DarkDragon]

+2

[STARGÅTE]

IncludePath is your frind,

so you can, select your directory und move relativ there

[luis]

And yet I hope to see this added,

Every time I have to do something like:

Code: Select all

IncludePath #PB_Compiler_FilePath
XIncludeFile "..\MyFile.pb"
XIncludeFile "..\MyFile2.pb"
XIncludeFile "..\..\MyFile3.pb"
IncludePath "."

or

Code: Select all

XIncludeFile #PB_Compiler_FilePath + "..\MyFile.pb"
XIncludeFile #PB_Compiler_FilePath + "..\MyFile2.pb"
XIncludeFile #PB_Compiler_FilePath + "..\..\MyFile3.pb"

when a

XIncludeFileRelative "..\file.ext"

could make everyone happy.

I don't really see why it was done this way in the first place. It's really counter-intuitive IMHO and make difficult create something you can move to another path or share with anyone (unless you use consistently the tricks mentioned above).

It's something minor since you can fix this way, but adding the command would require really... nothing I guess, so a request is understandable.


Thanks.

[Zach]

I have no problem backing out of my source directory and going into another using XincludeFile.... Nor do I have a problem navigating deeper into my source directory.. I maintain a "includes" directory where I place common reused code files, so I don't have to move things around, etc.. I thought that was just plain good practice.

What exactly is the benefit here? I have to agree I'm not understanding the request.

[luis]

The links listed in this thread already explains it, but anyway:

Code: Select all

c:\dira\dirb\includes
	
	c:\dira\dirb\includes\math\
		math1.pb
		math2.pb
	
	c:\dira\dirb\includes\support\
		support1.pb
		support2.pb

	c:\dira\dirb\includes\graph\
		graph1.pb
		graph2.pb
	

In your program's main include:

xincludefile "c:\dira\dirb\includes\math\math1.pb"
xincludefile "c:\dira\dirb\includes\graph\graph1.pb"

If math1.pb needs to include support1.pb I would like to be able to do (inside math1.pb obviously):

xincludefile "..\support\support1.pb"

Would be nice (and logical) and it will make your include tree easily moveable from place to place and shareable with other people.

But this DOES NOT WORK, because all paths are relative to the main program file.

Same thing if math1.pb tries to include math2.pb by simply using:

xincludefile "math2.pb"

They are both in the same dir, but no sir, because the path it's still relative to the main including file.

IMHO this is really flawed.


[EDIT: THIS REQUEST HAS BEEN IMPLEMENTED]

[Zach]

Ah.. I see what you mean, now.