Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] 'exporting' a workspace

Just as a matter of question, Eclipse allows one to export projects and
import them. You can even select e.g. to archive files or into a filesystem
etc., then it allows you to select, which projects to export.

Importing is just the other way around. You select from what you want to
import, e.g. archive, filesystem..., then select which projects found it
will import.

Does this not work for you? It should import every file which belongs to the
project and you selected. About the .metadata (compiler/debugger), hmm, try
it?

> --- Ursprüngliche Nachricht ---
> Von: "dmsubs" <dmsubs@xxxxxxxxxxxxx>
> An: "'Doug Schaefer'" <DSchaefer@xxxxxxx>, "'CDT General developers
> list.'" <cdt-dev@xxxxxxxxxxx>
> Betreff: RE: [cdt-dev] 'exporting' a workspace
> Datum: Thu, 19 Jan 2006 16:12:33 -0000
> 
> Ahh - that's an idea. I'll go and investigate.
> 
> Thanks for the tip.
> 
> ---
> Derek  
> 
> > -----Original Message-----
> > From: Doug Schaefer [mailto:DSchaefer@xxxxxxx] 
> > Sent: 19 January 2006 16:08
> > To: dmsubs@xxxxxxxxxxxxx
> > Subject: RE: [cdt-dev] 'exporting' a workspace
> > 
> > There may be a way to automate importing. This is more 
> > Eclipse platform stuff so I'm not sure. I've seen examples 
> > packaged as plugins that come with import wizards to set 
> > things up. There may even be some frameworks in the platform 
> > to help with this.
> > 
> > Doug Schaefer, QNX Software Systems
> > Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> >  
> > 
> > > -----Original Message-----
> > > From: dmsubs [mailto:dmsubs@xxxxxxxxxxxxx]
> > > Sent: Thursday, January 19, 2006 11:05 AM
> > > To: 'Doug Schaefer'; 'CDT General developers list.'
> > > Subject: RE: [cdt-dev] 'exporting' a workspace
> > > 
> > > Doug,
> > > 
> > > Yes, that would work, but doesn't give a good 'out of box' 
> > experience.
> > > What
> > > if I had 100 examples? A bit laborious for each customer to 
> > have to do 
> > > this.
> > > You also have to build dependencies for each project (in my 
> > example, 
> > > there is one project that all others are dependent on).
> > > 
> > > Another idea - Is there a way to automate the importing of projects 
> > > into a workspace (and add a dependency!).
> > > 
> > > Thanks
> > > ---
> > > Derek
> > > 
> > > > -----Original Message-----
> > > > From: Doug Schaefer [mailto:DSchaefer@xxxxxxx]
> > > > Sent: 19 January 2006 15:54
> > > > To: dmsubs@xxxxxxxxxxxxx; CDT General developers list.
> > > > Subject: RE: [cdt-dev] 'exporting' a workspace
> > > >
> > > > I'm not sure you can do it that way. The problem is that the 
> > > > .metadata directory in the workspace isn't really portable.
> > > > If you delete that directory in your distribution, your 
> > users should 
> > > > be able to import all of the projects using the import existing 
> > > > project wizard.
> > > >
> > > > Doug Schaefer, QNX Software Systems
> > > > Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> > > >
> > > > > -----Original Message-----
> > > > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > > > > On Behalf Of dmsubs
> > > > > Sent: Thursday, January 19, 2006 10:46 AM
> > > > > To: 'CDT General developers list.'
> > > > > Subject: [cdt-dev] 'exporting' a workspace
> > > > >
> > > > > Hi,
> > > > >
> > > > > I wish to deliver an "examples" workspace to my users 
> > as part of a 
> > > > > product delivery.
> > > > >
> > > > > The workspace consists of a dozen, or so, C/C++ projects.
> > > > They are a
> > > > > mixture
> > > > >
> > > > > of standard make and managed make projects. I can (and
> > > > have) zipped up
> > > > > the entire workspace directory and deliver that. However,
> > > > it contains
> > > > > references that are specific to my tools installation (such as 
> > > > > discovered include paths etc).
> > > > > There is
> > > > > also a lot of history and other stuff that is not relevent.
> > > > >
> > > > > Is there a simple way of exporting the relevant parts of
> > > > workspace? If
> > > > > not, what can I safely remove? I'm looking for a minimum set of 
> > > > > files/directories that describes the workspace/projects and
> > > > will lead
> > > > > to a succesful build.
> > > > >
> > > > > Thanks for your help,
> > > > >
> > > > >
> > > > > ---
> > > > > Derek
> > > > >
> > > > > _______________________________________________
> > > > > 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
> 

-- 
DSL-Aktion wegen großer Nachfrage bis 28.2.2006 verlängert:
GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl


Back to the top