Re: [Dltk-dev] Dymically adding include path entries

[Alex Panchenko <alex@xxxxxxxxx>]

Hi Robert,

Basically there are two approaches: 
a) specify all the include paths as external folders of the project (it's easier to implement. DLTK Ruby works this way)
b) dynamically add only used include files to the project (it's more work for you, but the project contains only really used files. DLTK Tcl follows this approach)

It's hard to say what is better for your language, it all depends.

Regards,
Alex

----- Original Message -----
From: "Robert Gruendler" <robert@xxxxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Thursday, March 11, 2010 5:29:23 PM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] Dymically adding include path entries

Hi all,

i've a general question about adding include paths to a project.

The framework i'm writing an extension has internal callbacks for
adding include paths, which can be any absolute path to a source
directory.

To parse libraries included in the project which are located outside
the project root, i would try to detect those paths in the source and 
add them to the include path during the build process.

I'm asking for advice if this approach is a bad idea (performance-wide),
or if i should prompt the user set the paths manually.


thanks

-robert
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev