I'm developing an android library which contains an external 3rd party library (for example: dagger).
I want to publish an .aar file to maven which not contains the dagger library inside. How can I create .aar file that doesn't contain any 3rd party libraries and contains only my code.
Another question, publishing .jar file instead of .aar file can solve this issue but there are any disadvantages is this solution?
Related
I am trying to add jaxb.index files to completely avoid the search for JAXB classes in my web service project and https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_tuning_jaxbcontext.html says that " If the package does not contain any JAXB classes, an empty jaxb.index file must be placed in the package". My EAR file contains third party jars and my web service project as utility jar in which I put jaxb.index file properly.
My question is that Does JAXB.newInstance search all classpath in which has third party jars not containing jaxb classes?
If yes it doesn't make sense to put empty jaxb.index to all package of third party jar such as logging. Does it?
I have 2 project
dll that include some other 3rd party dll and use them (don't have the sources - just using it)
some testing exe process that I using to check my dll that I developing
Now, I wrote simple class in the dll and I try to use this class instance on my exe tester - and I get an error about that the exe does not find the 3rd party include files that my dll include
How to solve it? How to import all the dependencies missing dll file to my tester exe?
There's no automated solution that I know of to retrieve include paths.
If you include an external header inside one of your DLL's headers, then it also becomes a dependency for your users. You need to abstract away that external code and not expose it in your interface in any way if you want to remove the dependency.
when creating a new module with
package create
it creates it using source code *.cs files, so as a result nuget package does not contain binaries, the source only
Is it any parameter or option to precompile module, so instead of source files, it will precompile DLL?
The only option I found, is to open package file (which is ZIP file) and update content manually, but this is not best solution
By design, Orchard modules are source code, to ensure that they are friendly to modification. If you want to deploy something without source code, it should be the whole site, not just one module. This can be done by building precompiled.
Considering a plugin system with the following installation pattern:
/install_prefix/main.exe
/install_prefix/plugins/plugin.dll
If my plugin depends on a library compiled as shared, its dll should be installed in the exe path:
/install_prefix/main.exe
/install_prefix/plugin_dependency.dll
/install_prefix/plugins/plugin.dll
I found isolated applications can be used to keep the dependency side by side with the plugin as follows:
/install_prefix/main.exe
/install_prefix/plugins/plugin_dependency.dll
/install_prefix/plugins/plugin.dll
This relies on a manifest file generated with visual. I am using cmake to generate my projects and I can't find any reference on a "good" way to handle isolated applications in a cmake file.
Did anybody have this use case?
EDIT:
This question propose answers on how to embed an already existing manifest file. What I would like is a way to generate the manifest file in the build process, in a perfect world with something as simple as installing exports. Something like:
install(
TARGETS target_name
MANIFEST target_name.manifest
)
This would generate the manifest file and embed it with the target.
I use third party static library (provided as a .LIB file without source code) in my project. For linking purposes it is enough to add it via "Properties/Linker/Input->Additional Dependencies"
This library is not used in any other project in the solution.
I wonder if I should add it as an item to project file itself. The advantages that I see: it will be immediately obvious that this project uses it and one wouldn't have to add it to version control system manually (anything that is a part of the project/solution is added automatically if you use something like AnkSVN).
The project in VCS must be buildable. It is impossible without the lib. So you should add it.