Often a package uses a library in the system, or more specifically, the
package is an interface to a library. The library should be installed as
well. There might be version problems but if the same OS and version is
used the only problem usually is whether the library is installed.
On Wednesday, May 13, 2015 at 8:10:59 AM UTC-3, vishnu suganth wrote:
>
> Thanks. That worked !!!
> Btw, what are the binary package dependencies ?
>
>
> On Tuesday, 12 May 2015 21:01:14 UTC+5:30, René Donner wrote:
>>
>> The packages are by default in ~/.julia/v0.3 (or v0.4 respectively).
>>
>> You can try to copy this over to Machine2 and see whether the packages
>> you need work that way.
>>
>> One thing that will be missing are binary package dependencies which are
>> installed using the package manager in a package's build step. When you see
>> errors on Machine2 referring to a package X, you can try to run
>> Pkg.build("X") and see whether Machine2 can install the dependencies.
>>
>> Hope that get's you started,
>>
>> Rene
>>
>>
>>
>> Am 12.05.2015 um 13:33 schrieb vishnu suganth <[email protected]>:
>>
>> > I have built Julia on a Machine1 and have added new packages such as
>> LightXML,TextPlots ( using Pkg.add("LightXML") ).
>> >
>> >
>> > I have ported the Julia binaries and libraries to another Machine2 (
>> same environment and OS ) and it works fine.
>> >
>> > How to copy the installed packages from Machine1 to Machine2 ? Where
>> are the packages getting installed in Machine1 ?
>> >
>> > Note: Machine2 cannot build any package from source nor it has internet
>> connectivity
>> >
>>
>>
