Jump to content


Importing Depencency to multiple streams and creating a release


  • Please log in to reply
1 reply to this topic

#1 oskarw90

oskarw90

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 15 May 2019 - 08:29 AM

Hi!

Im looking for info on how to do let multiple streams use a dependancy, thats located in another stream, and afterwards, creating a release candidate that we can build, with a single instance of that dependancy.

we are working in Unreal Engine 4, and the example is:

We have a plugin (1) that lets us communicate through serialport, which has its own stream.

we've built two other plugins (2 and 3) that utilizes that serial plugin, each of them are a seperate stream.

Those two new plugins/streams are created from the Serial port stream, using only share...


The problem we are having are when we are creating a new stream (a new project), and we want to utilize both of the 2 and 3 plugins.

We have been trying to use import+ to get both the 2 and 3 plugins mapped to a folder in a workspace, but since import overwrite eachother, we can only one or the other plugin.

we though an alternative would be to map 2 and 3 with their dependancies to seperate folders, but then we would get two instances of plugin 1 which would create issues in unreal engine.

it would be easy to just keep everything seperate and manually importing dependencies, but that would kind of defeat the purpose of every stream knowing its own dependancy, and we would have to refer to a large documentation sheet every time we wanted to create a new project.


Do you guys have any ideas on how to do this? or is perforce capable of doing it?

Best Regards
Oskar
- p4 beginner -

#2 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 800 posts

Posted 15 May 2019 - 08:49 PM

Quote

it would be easy to just keep everything seperate and manually importing dependencies, but that would kind of defeat the purpose of every stream knowing its own dependancy, and we would have to refer to a large documentation sheet every time we wanted to create a new project.

Ultimately I think this (tracking the dependencies yourself and setting up each stream to assemble the dependency tree correctly rather than attempting to use any kind of clever inheritance within the stream hierarchy) is your best bet.  Stream imports aren't really set up for managing dependency trees.

The other option would be to specify your stream Paths file-by-file to interleave the two imported streams into a single directory.  But: yech.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users