I have tried cloning Public\Common\OAK\Drivers\PCIBUS using two different methods:
1). via the MSDN article from Steve Maillet and Mike Hall, and
2). from Catalog Items View (CE6, Visual Studio 2005 SP1), right-click on "PCI Bus" item under device drivers/bus drivers and select "Clone Catalog Item".
Method 1 eventually worked, though I had to fool around with the sources files more than suggested in their article. This method does not create a sub-project in PB/VS. They have you puts things under _TARGETPLATROOT instead.
Method 2 creates a sub-project (two in fact--as it also creates a DefBusLib project) and seems more closely related to how you suggest cloning a project. However, simply building after cloning results in actually crashing the build (not just a build fail--it actually crashes the PB build component). It appears this clone option only does a portion of the work, though I haven't tracked down what is wrong yet. However, I note that it renames the libraries from their original name to with "_clone" appended.
Q1: what are the advantages/disadvantages of locating cloned drivers as a sub-project in OSDesigns vs. _TARGETPLATROOT?
Q2: does anyone actually use the catalog PB clone option for drivers, or would I end up needing to perform almost all the steps you show above anyway?
Q3: do you recommend renaming cloned drivers?
BTW: if anyone is curious, this is the error from method 2: "Platform Builder Platform Builder Dependency Discovery has encountered a problem and needs to close. We are sorry for the inconvenience."
Thanks for the instructions above--I'm going to try that as method 3.
Using Catalog to clone
I have tried cloning Public\Common\OAK\Drivers\PCIBUS using two different methods:
1). via the MSDN article from Steve Maillet and Mike Hall, and
2). from Catalog Items View (CE6, Visual Studio 2005 SP1), right-click on "PCI Bus" item under device drivers/bus drivers and select "Clone Catalog Item".
Method 1 eventually worked, though I had to fool around with the sources files more than suggested in their article. This method does not create a sub-project in PB/VS. They have you puts things under _TARGETPLATROOT instead.
Method 2 creates a sub-project (two in fact--as it also creates a DefBusLib project) and seems more closely related to how you suggest cloning a project. However, simply building after cloning results in actually crashing the build (not just a build fail--it actually crashes the PB build component). It appears this clone option only does a portion of the work, though I haven't tracked down what is wrong yet. However, I note that it renames the libraries from their original name to with "_clone" appended.
Q1: what are the advantages/disadvantages of locating cloned drivers as a sub-project in OSDesigns vs. _TARGETPLATROOT?
Q2: does anyone actually use the catalog PB clone option for drivers, or would I end up needing to perform almost all the steps you show above anyway?
Q3: do you recommend renaming cloned drivers?
BTW: if anyone is curious, this is the error from method 2: "Platform Builder Platform Builder Dependency Discovery has encountered a problem and needs to close. We are sorry for the inconvenience."
Thanks for the instructions above--I'm going to try that as method 3.