Comments (9)
possibly ... I'm not sure what LOE this would involve.
from netty-tcnative.
are we just blowing away the build artifacts when we FTP new code (or however we get new code)? can the build artifacts follow the typical build phases (mvn clean
destroys build artifacts, and otherwise they persist)?
from netty-tcnative.
are we just blowing away the build artifacts when we FTP new code (or however we get new code)?
If using ftp, probably ... if using the scm plugin (e.g boringssl), not sure.
can the build artifacts follow the typical build phases (mvn clean destroys build artifacts, and otherwise they persist)?
That would be ideal :) ... but sorting this out for each submodule (for both APR and SSL) will require some work.
from netty-tcnative.
I think we should restructure the project so the build artifacts are separated from the directories that get FTPed. The configure scripts should support specifying a prefix
or build directory right?
from netty-tcnative.
Which build artifacts are you referring to? APR and SSL? In some cases, we're already creating an install directory (using --prefix
when using automake). For ninja-based builds, we'd have to manually copy artifacts, but it's still doable.
from netty-tcnative.
Which build artifacts are you referring to?
things that are generated during the build (.o
, .a
, .class
, etc...) that can be inspected by build tools (make, maven, etc..) to avoid re-building if not necessary.
from netty-tcnative.
so APR and SSL?
from netty-tcnative.
APR and SSL
This statement was a bit vague and it was not clear what you were referring to. As long as you are implying the difference between source files obtained via the "get sources" step and the "artifacts generated during the build" step (.o
, .a
, .class
) then yes plus the tcnative artifacts.
It looks like the tcnative artifacts are also regenerated even with no change (not sure if it was like this before though?):
$ mvn install
...
$ ls -al ./boringssl-static/target/native-build/src/.libs/ssl.o
... Feb 24 10:25 ./boringssl-static/target/native-build/src/.libs/ssl.o
$ mvn install
...
$ ls -al ./boringssl-static/target/native-build/src/.libs/ssl.o
... Feb 24 10:36 ./boringssl-static/target/native-build/src/.libs/ssl.o
from netty-tcnative.
This was fixes by #390
from netty-tcnative.
Related Issues (20)
- Is there CVE-2017-12613 vulnerability in netty-tcnative? HOT 1
- netty-tcnative was built without FIPS support error while trying to build with openssl3 with fips module as default provider HOT 2
- Request for published builds of netty-tcnative-openssl-static on Maven central HOT 2
- netty-tcnative dynamically links to older OpenSSL libraries when multiple versions are present
- Hash-pin workflow GitHub Actions
- Memory leak and huge memory consumption on a file upload when upstream uses HTTP2 and downstream uses HTTP1 HOT 2
- SIGSEGV with netty-tcnative-boringssl-static v2.0.61.Final HOT 1
- Android 上无法进行使用 HOT 2
- Netty: SslProvider.OPENSSL_REFCNT example
- Suppressed: java.lang.UnsatisfiedLinkError: no netty_tcnative in java.library.path: /Users/peteaston/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. HOT 1
- SIGSEGV during SSL.freeSSL on netty-tcnative-boringssl-static v2.0.61.Final HOT 20
- Classifier ignored for statically linked libraries
- sys_siglist: symbol not found on alpine HOT 3
- Make OpenSSL engine configurable HOT 4
- Is it time to retire NPN? HOT 5
- netty-tcnative-boringssl-static does not depend on all native jars
- No release notes published?
- X25519Kyber768Draft00 named group not being picked up by boringssl static HOT 8
- Remove accesses to private field bio->num HOT 2
- Building tcnative with openssl v3.0.9 throwing an error: Your version of OpenSSL is not compatible with this version of tcnative
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from netty-tcnative.