www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - installation and configuration of vibe

reply "Tyro[17]" <nospam home.com> writes:
I attempted once to install DMD on OSX using the .dmg installer but it 
wasn't available. Since then I've simply downloaded the zip file, unzip 
it into /usr/share/dmd and create two symlinks to DMD and RDMD in 
/usr/bin/. Installation instructions contained in the readme file of 
vibe suggests that I use the .dmg installer. Since I did not, I get the 
following error after executing vibe:

andrew:vibe andrew$ vibe
Error: module object is in file 'object.d' which cannot be read
import path[0] = /usr/share/vibe/bin/../source
import path[1] = source
import path[2] = /tmp
Failed: 'dmd' '-g' '-w' '-property' '-I/usr/share/vibe/bin/../source' 
'-L-levent_pthreads' '-L-levent' '-L-lssl' '-L-lcrypto' '-Jviews' 
'-Isource' '-v' '-o-' '/tmp/vpm.d' '-I/tmp'

what do I need to do to configure vibe so that it can finds the D 
installation without using this installer?
Oct 25 2012
parent reply Jacob Carlborg <doob me.com> writes:
On 2012-10-25 11:23, Tyro[17] wrote:
 I attempted once to install DMD on OSX using the .dmg installer but it
 wasn't available. Since then I've simply downloaded the zip file, unzip
 it into /usr/share/dmd and create two symlinks to DMD and RDMD in
 /usr/bin/. Installation instructions contained in the readme file of
 vibe suggests that I use the .dmg installer. Since I did not, I get the
 following error after executing vibe:

 andrew:vibe andrew$ vibe
 Error: module object is in file 'object.d' which cannot be read
 import path[0] = /usr/share/vibe/bin/../source
 import path[1] = source
 import path[2] = /tmp
 Failed: 'dmd' '-g' '-w' '-property' '-I/usr/share/vibe/bin/../source'
 '-L-levent_pthreads' '-L-levent' '-L-lssl' '-L-lcrypto' '-Jviews'
 '-Isource' '-v' '-o-' '/tmp/vpm.d' '-I/tmp'

 what do I need to do to configure vibe so that it can finds the D
 installation without using this installer?

I suggest you first try and compile a simple Hello World in D : // main.d module main; import std.stdio; void main () { writeln("Hello World"); } $ dmd main.d -- /Jacob Carlborg
Oct 25 2012
next sibling parent reply "Tyro[17]" <nospam home.com> writes:
On 10/25/12 5:45 AM, Jacob Carlborg wrote:
 On 2012-10-25 11:23, Tyro[17] wrote:
 I attempted once to install DMD on OSX using the .dmg installer but it
 wasn't available. Since then I've simply downloaded the zip file, unzip
 it into /usr/share/dmd and create two symlinks to DMD and RDMD in
 /usr/bin/. Installation instructions contained in the readme file of
 vibe suggests that I use the .dmg installer. Since I did not, I get the
 following error after executing vibe:

 andrew:vibe andrew$ vibe
 Error: module object is in file 'object.d' which cannot be read
 import path[0] = /usr/share/vibe/bin/../source
 import path[1] = source
 import path[2] = /tmp
 Failed: 'dmd' '-g' '-w' '-property' '-I/usr/share/vibe/bin/../source'
 '-L-levent_pthreads' '-L-levent' '-L-lssl' '-L-lcrypto' '-Jviews'
 '-Isource' '-v' '-o-' '/tmp/vpm.d' '-I/tmp'

 what do I need to do to configure vibe so that it can finds the D
 installation without using this installer?

I suggest you first try and compile a simple Hello World in D : // main.d module main; import std.stdio; void main () { writeln("Hello World"); } $ dmd main.d

How the most obvious things elude us. I recently switched from placing "alias dmd=/usr/share/dmd/osx/bin/dmd" .bash_profile (which has worked perfectly for me since I bought my MAC) to placing the symlinks in /usr/bin/. Typing DMD and RDMD at the terminal window and seeing help and usage information for both programs display properly, I assumed that they work. But since moving from the command line interface to Alexander Bothe's awesome Mono-D ide a little while back, I haven't compiled anything at the command line so hadn't realized that it wasn't working. Long story short, it does not compile... I wasn't expecting to anything else since the simple one liner placed in .bash_profile took care of the issue. What am I missing?
Oct 25 2012
parent reply Jacob Carlborg <doob me.com> writes:
On 2012-10-25 12:20, Tyro[17] wrote:

 How the most obvious things elude us. I recently switched from placing
 "alias dmd=/usr/share/dmd/osx/bin/dmd" .bash_profile (which has worked
 perfectly for me since I bought my MAC) to placing the symlinks in
 /usr/bin/. Typing DMD and RDMD at the terminal window and seeing help
 and usage information for both programs display properly, I assumed that
 they work. But since moving from the command line interface to Alexander
 Bothe's awesome Mono-D ide a little while back, I haven't compiled
 anything at the command line so hadn't realized that it wasn't working.

 Long story short, it does not compile...
 I wasn't expecting to anything else since the simple one liner placed in
 .bash_profile took care of the issue. What am I missing?

You may need to create a symlink for the dmd.conf file as well, it's located next to the dmd binary. Double check that the dmd.conf file looks correct, when it's located in the zip it expects the src directory to be two levels up. Alternative you can try out DVM: https://bitbucket.org/doob/dvm "DVM allows you to easily download and install D compilers and manage different versions of the compilers." -- /Jacob Carlborg
Oct 25 2012
parent Jacob Carlborg <doob me.com> writes:
On 2012-10-26 00:03, Tyro[17] wrote:

 Just got around to looking back at this. That was in fact the piece of
 missing information. I never linked to or modified the dmd.conf file.
 Every thing works great now. Thanks for the DMV info but I prefer to do
 this manually. This way I'll never have to worry about an installer
 package being broken or unavailable. Besides, once you know what to do,
 this is pretty simple.

Sure, but when you built the tool/installer and know how it works :) it's pretty nice to not have to do it manually each time. -- /Jacob Carlborg
Oct 25 2012
prev sibling parent "Tyro[17]" <nospam home.com> writes:
On Thursday, 25 October 2012 at 11:15:38 UTC, Jacob Carlborg 
wrote:
 On 2012-10-25 12:20, Tyro[17] wrote:

 How the most obvious things elude us. I recently switched from 
 placing
 "alias dmd=/usr/share/dmd/osx/bin/dmd" .bash_profile (which 
 has worked
 perfectly for me since I bought my MAC) to placing the 
 symlinks in
 /usr/bin/. Typing DMD and RDMD at the terminal window and 
 seeing help
 and usage information for both programs display properly, I 
 assumed that
 they work. But since moving from the command line interface to 
 Alexander
 Bothe's awesome Mono-D ide a little while back, I haven't 
 compiled
 anything at the command line so hadn't realized that it wasn't 
 working.

 Long story short, it does not compile...
 I wasn't expecting to anything else since the simple one liner 
 placed in
 .bash_profile took care of the issue. What am I missing?

You may need to create a symlink for the dmd.conf file as well, it's located next to the dmd binary. Double check that the dmd.conf file looks correct, when it's located in the zip it expects the src directory to be two levels up. Alternative you can try out DVM: https://bitbucket.org/doob/dvm "DVM allows you to easily download and install D compilers and manage different versions of the compilers."

Just got around to looking back at this. That was in fact the piece of missing information. I never linked to or modified the dmd.conf file. Every thing works great now. Thanks for the DMV info but I prefer to do this manually. This way I'll never have to worry about an installer package being broken or unavailable. Besides, once you know what to do, this is pretty simple. Thanks
Oct 25 2012