[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] First gotcha with add/exclude children of FFS
|
I created an ecproj project and used the Team support to add it to CVS, commit some changes, etc. There could be other problems of course but at least the basics seemed to work.
- Ken
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Schaefer, Doug
Sent: Thursday, January 24, 2008 8:48 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
I guess my concern over team support is that it won't work with the EFS solution either. I'll need to investigate a bit more to see what the root issue is.
Doug
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ken Ryall
Sent: Wednesday, January 23, 2008 6:27 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] First gotcha with add/exclude children of FFS
Doug,
I discussed this with Warren and Ed today and we remain skeptical that linked resources will be a viable solution, mostly because of the team support bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=41929 P5 RESOLVED LATER
On the other hand Ed pointed out that my question was probing in the wrong direction, a better solution would be to have an EFS representation of the actual project structure. In our case we already have some files that describe the contents of the project. Warren is going to investigate using these to populate an EFS file system. If that works we'll see if it is something we can generalize for CDT.
- Ken
> From: "ext Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> Date: Wed, 23 Jan 2008 11:49:09 -0800
> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>
> Sure. Hi!
>
> The main driver for our work is that we have a lot of customers that
> have huge trees of source and they want to pick and chose out those
> trees files and folders to include in the project. You often use
> linked resource for this, but there are cases where you may want
> directories high up in the three but want to chop off branches. In the
> EFS sense, this would mean hiding (or excluding) children when
> reporting getChildNames(). Is this what isHidden is for? Or am I misinterpreting things.
>
> Thanks,
> Doug.
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Szymon Brandys
> Sent: Wednesday, January 23, 2008 2:36 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>
> Doug,
>
> Could you elaborate more on the excluded resources? I added the "hidden"
> resources,
> so maybe I can help you.
> --
> Szymon Brandys
> Staff Software Engineer
> szymon.brandys@xxxxxxxxxx
> (+48 12) 628 9857
>
> IBM SWG Lab, Cracow, Poland
> IBM Polska Sp. z o.o. oddział w Krakowie ul. Armii Krajowej 18 30 -150
> Kraków
>
> NIP: 526-030-07-24
> Sąd Rejonowy dla m.st. Warszawy, XIII Wydział Gospodarczy KRS KRS
> 0000012941, Kapitał zakładowy: 3.073.600 PLN
>
>
>
> "Schaefer, Doug"
> <Doug.Schaefer@wi
> ndriver.com> To
> Sent by: "CDT General developers list."
> cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
> clipse.org cc
>
> Subject
> 2008-01-23 20:17 RE: [cdt-dev] First gotcha with
> add/exclude children of FFS
>
> Please respond to
> "CDT General
> developers list."
> <cdt-dev@eclipse.
> org>
>
>
>
>
>
>
> Not only that, I've just found a isHidden attribute on IResource that
> appears to want to do the exclude side. I'll see what I can find.
> There doesn't appear to be UI for it.
>
> Doug.
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Szymon Brandys
> Sent: Wednesday, January 23, 2008 1:53 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>
> // Maybe I missing something but I don't see a way to create a
> resource and then // set its underlying URI. Have you looked into this?
>
> Right, linked resources should be used in this case.
>
> --
> Szymon Brandys
>
>
>
>
>
> "Schaefer, Doug"
>
> <Doug.Schaefer@wi
>
> ndriver.com>
> To
> Sent by: "CDT General developers list."
>
> cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
>
> clipse.org
> cc
>
>
>
> Subject
> 2008-01-23 16:43 RE: [cdt-dev] First gotcha with
>
> add/exclude children of FFS
>
>
>
> Please respond to
>
> "CDT General
>
> developers list."
>
> <cdt-dev@eclipse.
>
> org>
>
>
>
>
>
>
>
>
>
> No I hadn't completed that piece. But at any rate, I'm concluding that
> linked resources are the way to go for doing the add part. The use
> case is pretty much identical and there is actually more support for
> linked resources than if we hid it at the EFS layer. I am aware that
> support for linked resources is incomplete and we could probably use a nicer UI for adding them in.
>
> My next step is to implement an excluded resources patch for the
> platform with a backup EFS implementation in case we can get the
> platform solution done in Ganymede.
>
> Thoughts?
>
> Cheers,
> Doug
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of ken.ryall@xxxxxxxxx
> Sent: Tuesday, January 22, 2008 6:09 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>
> Doug,
>
> I was playing around with the FFS support and run into another issue
> that you may have thought about already:
>
> Assuming that you did want to add a file to a project that was in an
> arbitrary location in the ecproj file system, how would you do it?
> Maybe I missing something but I don't see a way to create a resource
> and then set its underlying URI. Have you looked into this?
>
> Thanks - Ken
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of ext Schaefer, Doug
> Sent: Monday, January 14, 2008 10:31 AM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>
> Yes. Ken mentioned that one at the CDT summit. We should take a look
> and try to understand why team team went that way, and, hopefully,
> give them a hand a solving it. I'm afraid it might be something
> intrinisicly wrong with the architecture, though. And I have doubts
> that the EFS solution would be much better.
>
> Doug
>
>
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx
>> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
>> Warren.Paul@xxxxxxxxx
>> Sent: Monday, January 14, 2008 11:24 AM
>> To: cdt-dev@xxxxxxxxxxx
>> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>>
>> I forget all of the issues that we ran into with linked resources,
>> but
>
>> I think there are tons of Bugzilla's logged against them. The major
>> issue I recall was that linked files/folders were not recognized by
>> the team support!
>>
>> Thanks,
>> Warren
>>
>>
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx
>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of ext Schaefer, Doug
>> Sent: Monday, January 14, 2008 10:17 AM
>> To: CDT General developers list.
>> Subject: RE: [cdt-dev] First gotcha with add/exclude children of FFS
>>
>> I'm sure we'll run into these types of problems with linked resources
>> or the EFS add files. I just think that linked resources are ahead of
>> the game since they've been around longer.
>>
>> So any help would be appreciated. What we really have to look out for
>> are cases where we're assuming the physical file layout is the same
>> as
>
>> the IResource hierarchy.
>>
>> As well, I'm thinking a nicer UI around linked resources would be
>> helpful, possibly a menu at the top level, Add Linked File/Folder.
>>
>> Doug Schaefer
>> Engineering Manager, Wind River Systems and Eclipse CDT Project Lead
>>
>>
>>> -----Original Message-----
>>> From: cdt-dev-bounces@xxxxxxxxxxx
>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ken Ryall
>>> Sent: Monday, January 14, 2008 2:02 AM
>>> To: CDT General developers list.
>>> Subject: Re: [cdt-dev] First gotcha with add/exclude children of FFS
>>>
>>> Doug,
>>>
>>> A while back we tried using linked resources and ran into a
>> number of
>>> problems that led us to abandon that approach. I can't
>> recall all of
>>> the details but in general we found linked resources to be
>> a bit of a
>>> hack with uneven support in both CDT and the platform and
>> in general
>>> are not treated as first class citizens.
>>>
>>> We really need a way out of this problem so let me know if
>> I can help
>>> look into anything.
>>>
>>> Thanks - Ken
>>>
>>>
>>>> From: "ext Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
>>>> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>>> Date: Fri, 11 Jan 2008 11:48:58 -0800
>>>> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>>> Conversation: [cdt-dev] First gotcha with add/exclude
>>> children of FFS
>>>> Subject: RE: [cdt-dev] First gotcha with add/exclude
>> children of FFS
>>>>
>>>> Yes. In a lot of ways, the adds are the same as linked
>>> resources, just
>>>> done at the file system level.
>>>>
>>>> Having said that, I'm starting to rethink that strategy.
>>> Why not just
>>>> use linked resources? This bug with managed build doesn't
>> happen in
>>>> that case (I remember the team working on fixing that). Any
>>> opinions?
>>>> I'll give it some thought over the weekend. Things would be
>>> simpler if
>>>> I was only had to worry about exclusions.
>>>>
>>>> Doug Schaefer
>>>> Engineering Manager, Wind River Systems and Eclipse CDT
>> Project Lead
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: cdt-dev-bounces@xxxxxxxxxxx
>>>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Chris Recoskie
>>>>> Sent: Friday, January 11, 2008 2:40 PM
>>>>> To: CDT General developers list.
>>>>> Subject: Re: [cdt-dev] First gotcha with add/exclude
>>> children of FFS
>>>>>
>>>>> This was something I was going to ask... so the FFS hierarchy is
>>>>> virtual then? I.e. it's not strictly a filter that hides
>>> files, you
>>>>> can also add files in arbritary folders in the hiearchy,
>>> even if the
>>>>> folder is not the actual parent of the file with respect to the
>>>>> operating system's view of the filesystem?
>>>>>
>>>>> ===========================
>>>>>
>>>>> Chris Recoskie
>>>>> Team Lead, IBM CDT Team
>>>>> IBM Toronto
>>>>> http://www.eclipse.org/cdt
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Schaefer, Doug"
>>>>>
>>>>> <Doug.Schaefer@wi
>>>>>
>>>>> ndriver.com>
>>>>> To
>>>>> Sent by: "CDT General
>>>>> developers list."
>>>>> cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
>>>>>
>>>>> clipse.org
>>>>> cc
>>>>>
>>>>>
>>>>>
>>>>> Subject
>>>>> 01/11/2008 02:08 [cdt-dev] First gotcha
>>>>> with
>>>>> PM add/exclude children
>>>>> of FFS
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Please respond to
>>>>>
>>>>> "CDT General
>>>>>
>>>>> developers list."
>>>>>
>>>>> <cdt-dev@eclipse.
>>>>>
>>>>> org>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> **** Build of configuration Debug for project Test ****
>>>>> **** Internal Builder is used for build ****
>>>>> g++ -O0 -g3 -Wall -c -fmessage-length=0 -otestdir\test.o
>>>>> ..\testdir\test.cpp
>>>>> g++: ..\testdir\test.cpp: No such file or directory
>>>>> g++: no input files
>>>>> Build error occurred, build is stopped Time consumed: 158 ms.
>>>>>
>>>>> Sigh.
>>>>>
>>>>> Of course, I've added the testdir directory from somewhere
>>> outside my
>>>>> project. Managed build obviously is assuming that the
>>> physical tree
>>>>> looks like the IResource tree. As Chris mentioned on the call
>>>>> yesterday, we're going to find a lot of these...
>>>>>
>>>>> Doug Schaefer
>>>>> Engineering Manager, Wind River Systems and Eclipse CDT
>>> Project Lead
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>> cdt-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>> cdt-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
