Project

General

Profile

Feature #9552

how to build libp2j such that it can be deployed to multiple different versions of the target platform

Added by Greg Shah over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Runtime Infrastructure - Support #4549: reduce/eliminate installation dependencies New

History

#1 Updated by Greg Shah over 1 year ago

Today, it is expected that when you build libp2j, you do so on the same or equivalent system to the target platform on which you are going to execute code that uses libp2j. For example, if you are going to run libp2j on Ubuntu 22.04_03 LTS then you must build libp2j on Ubuntu 22.04_03 LTS. Building on Ubuntu 16.10 probably won't work at all and even building on Ubuntu 22.04_02 LTS may not work.

I don't know that we document this.

It would be better if we had a build that could be done once for all 64-bit Linux platforms (at least those with certain minimum requirements). I think this can be achieved using static linking and some careful choices but this task is meant to test out and implement that approach.

This would be the objective for both Linux and Windows. We are not trying to cross-compile (Windows builds on Linux). We are just trying to implement a single build for Linux in which the binary can be used across 64-bit Linux platforms AND a single build for Windows in which the binary build can be used across Windows platforms.

#2 Updated by Greg Shah over 1 year ago

  • Related to Support #4549: reduce/eliminate installation dependencies added

Also available in: Atom PDF