Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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,
> -----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

Back to the top