software-distribution

JSmooth question on bundling a JRE

夙愿已清 提交于 2019-12-06 01:20:32
问题 I'm trying to bundle a JRE with my jar file so that I can run my application on any windows computer, regardless of if it has Java or not. The jsmooth manual says: For the option to work correctly, you have to put a JRE in a directory near the EXE (generally in a subdirectory called "jre" or whatever). Once the exe is generated, it will FIRST try to locate the JRE at the location mentioned. If it can't be found there, then it will fallback in the normal jre look-up mode (search for a jre or a

CMake: build cross-platform distribution

女生的网名这么多〃 提交于 2019-12-04 16:55:56
On my MacOSX I've developed an application that makes use of Qt and VTK libraries. I generate the makefile using CMake. Now I want to compile an end-user self-contained package on Windows, and it is supposed to work on end-user machine without needing to pre-install Qt or VTK libraries. I think is possible to do this by modifying the CMakeLists.txt file but a web search hasn't pointed me the right direction. How to make a distributable package for Windows using CMake? André What I have done in one of my own projects is write a little script which will give me the .so files or .dll files from

Packaging an application that uses the ImageMagick C API

人走茶凉 提交于 2019-12-04 09:40:18
I've created a little Windows app that uses the ImageMagick C API but have run into a bit of a brick wall. The app works fine and I'm ready to share it with a few others in our organisation but I can't find documentation on distributing such an app without installing ImageMagick on the target machine. Does anyone here have information, or a link to information, that details how to package this up for distribution? What DLLs are required and which one(s) need to registered with Windows? The target users will be on a mix of XP and Win7. I had to do something similar, though I built Imagemagick

Local collection of Python packages: best way to import them?

余生长醉 提交于 2019-12-04 04:20:04
问题 I need to ship a collection of Python programs that use multiple packages stored in a local Library directory: the goal is to avoid having users install packages before using my programs (the packages are shipped in the Library directory). What is the best way of importing the packages contained in Library ? I tried three methods, but none of them appears perfect: is there a simpler and robust method? or is one of these methods the best one can do? In the first method, the Library folder is

How to I organize my pytest tests if I'm not distributing them with my package?

Deadly 提交于 2019-12-04 04:01:06
问题 As suggested in the pytest documentation, I have set up my package with the intent not not distributing my tests along with my package: setup.py mypkg/ __init__.py mypkg/ appmodule.py tests/ test_app.py ... but I am confused about how to ensure that these tests will run correctly when present (e.g. on Travis CI, or in clones of the project directory). I want the imports in my test scripts to apply to the source in the adjacent mypkg/ directory (and not to any mypkg that might be installed in

Creating multi-platform CDs for software distribution

主宰稳场 提交于 2019-12-03 21:19:46
This is not strictly programming related, but I hope still relevant. I'm working on a project which is written in Java and intended for use on PCs and Macs. It will be distributed on CD (and perhaps DVD, eventually). Our intended audience is decidedly non-technical and, as such, it's important the CD "just work" when it's loaded. This is not itself difficult. For Windows, we can setup Autorun to automatically launch the app and, for Mac, we can use special folder formatting to make it clear what the user should do. The hitch is that we would like to ship one disc which could be used on either

Gradle Distribution Task Output Files Not at Root of ZIP

守給你的承諾、 提交于 2019-12-03 10:28:22
I created a simple Gradle build that exports the contents of ./src/main/groovy to a zip file. The zip file contains a folder with the exact same name as the zip file. I cannot figure out how to get the files into the root of the zip file using the distribution plugin. i.e. gradlew clean distZip produces: helloDistribution-1.0.zip -> helloDistribution-1.0 -> files what I would like: helloDistribution-1.0.zip -> files My build.gradle file: apply plugin: 'groovy' apply plugin: 'distribution' version = '1.0' distributions { main { contents { from { 'src/main/groovy' } } } } I have attempted to fix

Serial number (registration key) algorithm in .NET [closed]

十年热恋 提交于 2019-12-03 10:03:39
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 4 years ago . There have been a few timely posts about IP security and the like, but none that I can find that specifically address an algorithm. In one of my current projects, we've decided to go the route of an offline registration key system. I imagine most of our eventual user base will be

Does it make sense to install my Python unit tests in site-packages?

笑着哭i 提交于 2019-12-03 07:27:10
I'm developing my first Python distribution package. My learning curve on Python packaging seems to be leveling off a bit, but I'm still wrestling with a few open questions. One is whether I should cause my unit tests to be installed alongside my code. I understand it's important to include tests in a source distribution . What I'm wondering is whether I should actually configure them to be installed? I've seen at least one popular package that appears to do this on purpose ( PyHamcrest ), and at least one other that appears to do it by accident ( behave ). So my (multi-part) question is this:

How to organize Python modules for PyPI to support 2.x and 3.x

天大地大妈咪最大 提交于 2019-12-03 06:42:41
问题 I have a Python module that I would like to upload to PyPI. So far, it is working for Python 2.x. It shouldn't be too hard to write a version for 3.x now. But, after following guidelines for making modules in these places: Distributing Python Modules The Hitchhiker’s Guide to Packaging it's not clear to me how to support multiple source distributions for different versions of Python, and it's not clear if/how PyPI could support it. I envisage I would have separate code for: 2.x 2.6 (maybe, as