I've successfully installed Caffe2 on my TX2 with jetPack by NVIDIA.
I am trying to figure out if I could make a folder that's not under my caffe2 installation folder (where caffe2 is installed) and make a new cmake project.
How does one connect the libraries from that root caffe2 folder to execute in that folder that's not under the installation folder?
Thanks!
I am not sure if I understand the question.
If you want to replace a Caffe2 dependency (like a library) by a library that comes from your project, you can do that by setting LD_LIBRARY_PATH accordingly.
Related
I'm using composer to load all my dependencies for my Yii2 application.
I also manage bower stuff with composer using Asset Packagist.
If I roll out my appication to an different system, I notice, that the same composer.json generates different ressouce directories.
Example:
I load the rowGrid library from Asset Packagist using the following line in the composer.json file:
"bower-asset/rowGrid.js": "1.0.6",
On my development machine this creates an folder like this /path/to/vendor/stuff/bower-asset/rowGrid.js.
Running the same composerfile on different machine, composer creates the following path for the rowGrid library: path/to/vendor/stuff/bower-asset/rowgrid.js. Here, there is an smal g in rowgrid.js, which results in problems, if the application tries to access die rowGrid library.
Why does composer uses different path-names?
...and how could I handle this problem?
//Edit:
Is there a way to define a target directors for a specific bower-library?
To answer my own question in the case that someone have the same issue:
On system A, the bower asset rowGrid was installed a long time ago from fxp Asset Packagist. (don't know, if this is important) At this time, die downloaded library rowGrid was installed into the bower-asset Path: vendor/bower-asset/rowGrid.js This is also set/documented at the ìnstalled.json file.
Removing the global installed "fxp Asset Packagist"-Plugin did not change anything, because the mapping, where to install rowGrid.js, was untouched in the installed.json. Also composer update did not change anything.
But: removing the package rowGrid from system a also removed the mapping at the installed.json. On re-installing rowGrid library again, composer fetched the same version from Asset Packagist but probably received also the new installation path, which is now lowercase: rowgrid.js/. The library is now installed in vendor/bower-asset/rowgrid.js
The same (last step) was happens on system b: fetching the current package with the same rowGrid release number as system a, which was installed in vendor/bower-asset/rowgrid.js .
I am developing a game in xcode using cocos2d-x i want to convert the .xcodeproj file to .apk file for that i use the Stella SDK. after download the package I try to configure it. But i am getting the following error, I typed in terminal.Please help me.
mac-man:~ srikanthreddy$ cd / opt
mac-man:/ srikanthreddy$ git clone https://github.com/morningtec/StellaSDK.git
fatal: could not create work tree dir 'StellaSDK'.: Permission denied
You are trying to clone the git project into /opt which is a directory that you may not have write permission for.
Usually you'd create such projects in your home directory, so try this instead:
mkdir ~/StellaSDK
cd ~/StellaSDK
git clone https://github.com/morningtec/StellaSDK.git
Note that this step is only cloning the StellaSDK project, it has nothing to do with the task you described (creating an .apk file). From that I take it you haven't fully understood that StellaSDK is a game engine / framework just like cocos2d-x, so you can't use that to create an .apk file unless you start a new project. In particular you can't just convert a .xcodeproj to work with Stella SDK, there is no automatism like that.
While at the same time cocos2d-x is a cross-platform engine capable of creating Android .apk apps. The reason why you're trying to use Stella for (or in place of?) an already existing cocos2d-x project is a bit of a mystery to me.
I have a solution that is primarily developed in Visual Studio 2012. I would like to develop in MonoDevelop without major incompatibilities.
Thus far, I have installed mrward's nuget addin for MonoDevelop and things work if I manually add each package in packages.config through that interface. However, this is highly onerous. This addin doesn't have support for automated package restore as of this writing.
I downloaded nuget.exe from CodePlex ("NuGet command line utility", as it's labeled). I use a simple find/xargs combination to install all required packages:
find . -name packages.config | xargs -I '{}' mono nuget.exe install '{}'
This creates several dozen directories in the directory from which it is run instead of putting things under packages/ as expected, and it also doesn't touch the project files so MonoDevelop still thinks that it should be looking for package references in the directory from which MonoDevelop was started.
I therefore opened MonoDevelop from the working directory that contains all of these package folders, and I still get invalid references. I think this is probably because the project is looking for package_name/ reference, but the folders are name package_name.version/ in the working directory.
Any suggestions for a sane, simple way to interact with this solution? I'm next going to try modifying my shell command so that it automatically drops to project/packages and runs nuget from that directory.
Did you try using the -o command line parameter with NuGet.exe? You can use that to get the packages to install into a particular packages folder.
The NuGet addin for MonoDevelop supports package restore from version 0.6 or above. Right click your project and select Restore Packages. This will download all the packages defined in your packages.config for all projects in the solution. It uses NuGet.exe to do this.
Another way to get this working is to use the custom NuGet MSBuild target so the package restore happens at build time when using xbuild. It would require some manual editing of project files though. Under the covers the custom MSBuild target just uses NuGet.exe with a similar command line to what you have already just with the output directory option specified. So I would try the command line approach since that will be less work.
You would have to get the following files from the NuGet repository on codeplex:
NuGet.exe
NuGet.targets
NuGet.config
Put these in a directory somewhere. Typically these are put in a .nuget directory in the same directory as your solution file. Then you need to edit your project files to include the NuGet.targets file and also define the SolutionDir property. So something like this:
<SolutionDir Condition="$(SolutionDir) == '' Or $(SolutionDir) == '*Undefined*'">..\..\</SolutionDir>
<Import Project="$(SolutionDir)\.nuget\NuGet.targets" />
You will also need to enable package restore on your machine. You can do this using the NuGet addin for MonoDevelop in the Options dialog. Under Linux this is available from the Edit menu under Preferences. Then look in the NuGet - General options and there is a checkbox for enabling package restore.
There is an example project on GitHub created by Jonathan Channon which uses package restore and works when building with xbuild inside MonoDevelop. There is also an issue on GitHub about using NuGet restore on Linux which might be helpful.
Update: 2014-05-14: NuGet addin for MonoDevelop now supports package restore.
I am just rewriting the question here:
I am building a console app that uses MySql connector. So I add reference to the dll in the project. When I compile the solution, I get an exe that runs fine on my own machine, but when I copy the exe to another machine, it doesn't work, because it can't find the Mysql dll. I have tried to copy the dll into the same folder as the exe on the other machine but no luck.
I also tried putting the dll in the same folder on same machines, but that didn't work either.
How do I deploy the dll correctly with my exe?
I had some different errors in the setup. It has to be the correct assembly dll (6.3.0) to work and also I needed to create the user#server and grant him privileges. But the dll is accessible when it's in the same folder as the exe.
I can't figure it out: do the files which are referenced in the Binary element of .wxs file get copied to the target machine, or are they resources of the install package?
They are definitely the resources of the install package. This means that they don't get installed to your application folder, but Windows Installer is supposed to extract it internally to some temporary location to address the functionality in it. And it is supposed to clean after itself. But this is definitely not visible to the end users of your installation.
At least, this is how I understand it.