[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Odp.: Build path/ Include path

Hi,

small explaination.
1. Include path view is used to build php.ini include_path for cli launch/debugging. It build own internal list and also update DLTK .buildpath libs and related projects. In past (before DLTK migration), was also used in similar way like DLTK Build Path.
2. Build path view is DLTK feature, works like JDT  Build Paths, it used to resolve SoureModules inside project (validation, index) and SourceModules from related projects/libs. For now PDT inject DLTK Source tab only (JDT Source)  in ugly way, without libs/projects/ordering.


-- 
Dawid PakuÅa

From: Thomas Gossmann <eclipse@xxxxxx>
Reply: PDT Developers <pdt-dev@xxxxxxxxxxx>
Date: 25 April 2016 at 10:27:13
To: PDT Developers <pdt-dev@xxxxxxxxxxx>
Subject:  Re: [pdt-dev] Odp.: Build path/ Include path

Hi,

my knowledge on include path (and also libraries) is very limited, I
think it just got copied in, when DLTK provided such functionality.
Reducing it to just build path is what would help PDT a lot. Then build
path would take 3 different types of entries:

- folder
- library folder
- project (see also [1])

[1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=492187

gossi

Am 24.04.16 um 20:56 schrieb Michal Niewrzal:
> Hi,
>
>
> My knowledge about include path management is very limited but +1 for
> every simplification around include path/build path &#X1f60a
>
>
> Michal
>
> ------------------------------------------------------------------------
> *Od:* pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> w
> imieniu uÅytkownika Dawid PakuÅa <zulus@xxxxxxxxx>
> *WysÅane:* 24 kwietnia 2016 18:31
> *Do:* PDT Developers
> *Temat:* [pdt-dev] Build path/ Include path
> Hi,
>
> Iâm playing with bug 444226 [1] and have two concerns.
>
> 1. Do we really need include path management in composer age, when PEAR
> is mostly dead? If yes can we just throw it away project provisional
> (see point 2) and keep it simple with âsync with build pathâ button/switch?
> 2. Rather than creating completly new widget (with ton of code to
> maintenance), maybe we could âjustâ migrate to standard DLTK
> BuildPathPropertyPage? + rename it to validation/index path. After that
> bug 472758[2] will be much simpler to resolve.
>
> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444226
> [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=472758
> --
> Dawid PakuÅa
>
>
> _______________________________________________
> pdt-dev mailing list
> pdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev

Attachment: smime.p7s
Description: S/MIME cryptographic signature