On Mon, Aug 16, 2010 at 9:43 AM, Fabio Zadrozny wrote:
> On Mon, Aug 16, 2010 at 10:33 AM, Ben Sunshine-Hill
> wrote:
> > On Mon, Aug 16, 2010 at 7:37 AM, Fabio Zadrozny
> wrote:
> >>
> >> In the 'project properties' there's a 'project references' item in the
> >> tree, that's where you should
On Mon, Aug 16, 2010 at 10:33 AM, Ben Sunshine-Hill wrote:
> On Mon, Aug 16, 2010 at 7:37 AM, Fabio Zadrozny wrote:
>>
>> In the 'project properties' there's a 'project references' item in the
>> tree, that's where you should put the referenced projects (so that one
>> project 'inherits' the pyth
On Mon, Aug 16, 2010 at 7:37 AM, Fabio Zadrozny wrote:
> In the 'project properties' there's a 'project references' item in the
> tree, that's where you should put the referenced projects (so that one
> project 'inherits' the pythonpath of another project).
>
> See: http://pydev.org/manual_101_pr
In the 'project properties' there's a 'project references' item in the
tree, that's where you should put the referenced projects (so that one
project 'inherits' the pythonpath of another project).
See: http://pydev.org/manual_101_project_conf2.html
Cheers,
Fabio
On Sat, Aug 14, 2010 at 2:11 PM,
Sorry, I misspoke. My issue isn't with the two PyDev projects -- for those,
I can just add a project reference, which seems to add the source folders to
the PYTHONPATH -- but with a makefile-based project in the workspace which
builds a .pyd that I'd like in the PYTHONPATH.
Ben
On Sat, Aug 14, 20
I have two PyDev projects in my workspace, one of which uses the other.
The "Source Folders" project properties tab says "Project source folders",
and won't let me add a reference to the other project.
The "External Libraries" tab says "External libraries... outside the
workspace", and requires p
