RE: [cdt-dev] 'exporting' a workspace

["dmsubs" <dmsubs@xxxxxxxxxxxxx>]

I've just thought of another reason why the workspace is useful to export -
launch configurations.

1. For each project, I have defined a debug configuration that sets up the
name of gdb (xx-elf-gdb) and parameters etc.
2. I have also defined an external tool that our users will use frequently.

I'm just trying to make life a bit easier for our first time users to get up
and running with a) eclipse/cdt, b) our tools and c) our examples!

Thanks,

---
Derek  

> -----Original Message-----
> From: dmsubs [mailto:dmsubs@xxxxxxxxxxxxx] 
> Sent: 19 January 2006 16:05
> 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