Platform-specific libs for C++ projects

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Platform-specific libs for C++ projects

Ganesan, Ramaprakash
Hello,

One of our teams, which work on C/C++ projects, have a requirement of using platform-specific 3rd party libraries (eg: ability to pull specific jars pertaining to Windows XP x86, or Windows 2008 R2 x64, or Solaris x64, etc.).
We want to understand the feasibility of hosting such 3rd party libraries on Artifactory, and some best practices behind implementing the same.

Have any of you implemented something on this kind?
Any recommendations as to how to structure repositories and form repository layouts (and/or properties) for such a use case?

Thank You and Best Regards

Ramaprakash
+91 9000034321
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Platform-specific libs for C++ projects

pscheir
Hi,

we use Artifactory for C++. But we do not have this use case yet.

The options I see are:

1. A folder indicating the Platform: You can introduce a dedicated field / folder via a custom layout: http://www.jfrog.com/confluence/display/RTF/Repository+Layouts

2. The type field to store the custom layout: http://www.jfrog.com/confluence/display/RTF/Repository+Layouts

3. Properties to store the layout:
https://www.jfrog.com/confluence/display/RTF/Using+Properties+in+Deployment+and+Resolution


If in your case primarily humans browse the repository I would rather not use properties. If you use the Platform information only for build automation I’d use properties.
My second choice would be an optional field in a custom layout.

Best regards, Peter


Ganesan, Ramaprakash wrote
Hello,

One of our teams, which work on C/C++ projects, have a requirement of using platform-specific 3rd party libraries (eg: ability to pull specific jars pertaining to Windows XP x86, or Windows 2008 R2 x64, or Solaris x64, etc.).
We want to understand the feasibility of hosting such 3rd party libraries on Artifactory, and some best practices behind implementing the same.

Have any of you implemented something on this kind?
Any recommendations as to how to structure repositories and form repository layouts (and/or properties) for such a use case?

Thank You and Best Regards

Ramaprakash
+91 9000034321
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users