|
Navigate to your workspace directory and look in the RemoteSystemsConnections folder. Under your profile name (your profile or team profile, whichever one you were using), there should be a CompileCommands folder. Under that are folders for various subsystems. The ibm.files400 folder stores the QSYS compile commands. Copy the xml file to the same location on another machine (other machines might have different profile names, but that should be ok). If you're using a source control repository such as CVS you can use Team synchronize to share the RemoteSystemsConnections project between different workspaces. This will let you share connection definitions, filters, compile commands and user defined actions. Cheers, Kushal Munir Websphere Development Studio Client for iSeries IBM Toronto Lab, 8200 Warden Ave., Markham, ON Phone: (905) 413-3118 Tie-Line: 969-3118 Email: kmunir@xxxxxxxxxx MichaelQuigley@Th eWay.org Sent by: To wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx idrange.com cc Subject 06/25/2004 02:12 [WDSCI-L] Compile commands PM Please respond to Websphere Development Studio Client for iSeries Does anyone know if there is a way to export and import Compile Commands? We've set up some custom compile commands and manually entering them for each source type on each workstation is very cumbersome. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.