I've decided to learn some assembly, however I haven't been able to figure out how to actually assemble it. I'm running OSX 10.6.8 with developer tools installed. I'm running Xcode 3.13, there's no downloads tab in the preferences in the version that I see and the download for command line tools from Apple's site doesn't run on anything less than 10.7.
I've seen some online sources saying that I should use the "as" "gas" or "gcc" commands, however terminal tells me that none of those commands exist. (to test, I simply opened a new terminal window and entered the command name with no parameters. I assume that would work but I could be mistaken.) I can't find any concrete documentation about whether or not this stuff is installed with developer tools/how to check if it is installed/where to install it.
Asking this question here was my last resort, however I'm sure the information was already out there and I just couldn't find it so if anyone could:
Explain why these commands don't work/what I should install if I want to assemble some basic assembly
Tell me how I could have figured this out on my own
I'd be really grateful. Thanks in advance.
[EDIT]There is a file named "as" in the Developer/usr/bin/ folder so I'm not sure why the command is not found. Do I have to do more than just navigate to the directory of the file I'm assembling and type "as filename"?
You wanted to check "UNIX development" when you installed Xcode. (How were you supposed to know this at the time?)
You can re-install Xcode, making sure to check that magic box.
However, the command-line drivers are actually present, they're just not in your path (they're in /Developer/usr/bin, if I remember right, though it's been a long time since I've tinkered around with Xcode 3.x). So you should be able to add that to $PATH and use them.
As a third alternative, you can always download a distribution of either gcc or clang.
Make sure that you have the Xcode "Command Line Tools" additional download installed. It's available in the Downloads tab of the Xcode preferences window.
Related
I have the same problem as the user who posted in "Unable to use Mathematica Link in NetLogo 6.0" (Unable to use Mathematica Link in NetLogo 6.0). For me, the Mathematica Link seems to work fine with Netlogo version 5.3.1. Even after I attempted the recommended hotpatch (which was the answer to the original posted question on this topic), still no luck (I get the same error message posted in the original comment cited above). I tried extracting the hotpatch in the NetLogo 6.0 directory and in the NetLogo 6.0 / app subdirectory... neither seemed to work. I'm using a PC with Windows 7.
Any advice on how to properly install the patch would be greatly appreciated.
This fix is packaged with 6.0.1 and instructions on using it can be found here. If it's easy for you to upgrade to 6.0.1 I would recommend doing that over trying to install the 6.0 fix. I have verified that the fix works for 6.0, although the installation instructions don't seem to be correct.
My configuration:
Windows 10 (don't have Windows 7 available, unfortunately)
NetLogo 6.0 64-bit
Windows 10 64-bit
The steps I took to install:
Before starting, go to your NetLogo installation directory and rename the "Mathematica Link" directory to "Mathematica Link - original" (or delete it, if you prefer).
When I downloaded the file, it extracted to somewhere in my Downloads folder. You may have to extract yourself, depending on your browser and OS configuration
I copied the enclosed "Mathematica Link" folder (the one with the space in the name, not the "MathematicaLink" folder at the top level) to the NetLogo directory (not the "app" directory as mentioned in the instructions).
I then opened Mathematica and ran the following commands:
File > Install > type: Package, source: From File, file: C:\Program Files\NetLogo 6.0.1\Mathematica Link\NetLogo.m, install name: NetLogo, install for this user only. Note that when selecting this file, Mathematica will use the last directory you opened, so when the file dialog opens, first navigate to the the top of the drive then navigate down to NetLogo 6.0.1 (using a NetLogo.m file from an older NetLogo version will almost certainly break Mathematica link, and this is a very easy mistake to make).
Entered in the notebook (cannot code block this): <
Entered in the notebook: NLStart["C:\\Program File\\NetLogo 6.0.1"] (note the double backslashes and no trailing backslash).
The NetLogo window will open after a noticeable delay (depending on your system speed and memory)
Edit:
I wanted to consolidate troubleshooting steps for future readers. I've introduced a new version of NetLogo.m available here, which users should download for troubleshooting purposes (it will be distributed with future versions of NetLogo). Some steps to using this:
Mathematica will cache old "NetLogo.m" files. You can find where these caches are by using the following commands in Mathematica:
FileNameJoin[{ $BaseDirectory, "Applications" }]
FileNameJoin[{ $UserBaseDirectory, "Applications" }]
Visit the directories obtained in Step 1 and delete all "NetLogo.m" files from them.
Download the new version of NetLogo.m
Install the downloaded version of NetLogo.m (and run <<NetLogo`)
Run NLDiagnostics["C:\\Program Files\\NetLogo 6.0.1"] to determine what paths are being searched. This function will produce a hash as an output. The key missingJars should be an empty list ({}).
If you want to check java version, you can run NLJavaDiagnostics[]. The javaVersion returned should start with "1.8.0", the javaArchitecture returned should be "64".
I'm building OSX commandline apps. it's almost complete.
source code is open'd in my github.
but I want to distribute its "binary(Execute file)" as free ware but I can't understand the method.
simply should I extract execute file and place my blog?
I'm sorry because my english is poor.
Make sure you are building a release version of your app as described here How to deploy a Mac Command Line Tool
Then you can place the binary on your blog or on any other page. Make sure you are not using any libraries that may be missing from other people Macs.
Note it is always helpful if you add a description what your app does, how it needs to be called (arguments, ...) and maybe give some screenshots or in case of a command line app textual version of outputs.
I've followed these directions exactly.
I was able to compile mingw32-make ycm_support_libs and it produced the necessary ycm_core.pyd, ycm_client_support.pyd, and libclang.dll files. However, I get this message when starting vim:
YCM libraries found in old YouCompleteMe/python location; please RECOMPILE YCM.
I have verified that all the tools I've used are 64bit version. Anything I find on the web about this just says to run ./install.sh --clang-completer, which should be doing exactly what mingw32-make ycm_support_libs does.
I was so close too! Any help?
The file that is produced from the compile doesn't need to be moved. This was an old instruction that is now obsolete. I've managed to get C/C++ auto-complete working on Windows 7.
https://github.com/Valloric/YouCompleteMe/issues/1172
From the above link: Oh I see... sorry :P Anyway I don't know when was the last time someone modified the wiki page on installing YCM on Windows. The wiki page is community maintained. The error is caused by the fact that before YCM was splitted in two repo (this one for the vim client, and one for the general backend, ycmd) the compiled libraries were putted in YouCompleteMe/python now instead are putted in YouCompleteMe/third_party/ycmd. Anyway we can continue to discuss this but I have to close this issue since is not a YCM bug and Windows is not supported officially.
I'm trying to just build webkit on windows. As usual I started with webkit site and trying to get developer tools setup. I'm struck basically at the cygwin Installation itself.
The cygwin-downloader gets all the packages and runs the setup normally.
As per the installation instructions, I selected the Install from Local Directory Option (cygwin install and source package directories are different).
There was some initial turbulance in finding the packages, somehow i could let it find the packages. The screen looks like this now.
I selected the packages (all) and then proceeded with next. It just ran very fast and exited saying nothing needs to be installed. It looked like this.
After I ran the cygwin shorcut from the desktop its shouting something is missing.
I don't understand what am I missing here. Also at some link it says we need a port to build webkit. If thats the case, how does anyone port webkit to their applications without building the webkit alone?
I know this is not a programming question. but this will help most of the people who are taking baby steps in understanding and build WebKit. Thanks!
According to this, it's seems a cygwin-downloader's bug.
However, there is a workaround...
Just copy {cygwin-downloader}\setup.ini file to a {cygwin-downloader}\x86\ directory. Then reopen setup.exe. It will show you a package list without turbulence. You don't need to click all from the package list. Just click Next.
I am trying to install the latest SVN Update OpenSceneGraph-3.1.4 on Mac OS X Mountain Lion.
Do I need to install a specific WindowSystemInterface ?
$ osgviewer cow.osg
View::setUpViewAcrossAllScreens() : Error, no WindowSystemInterface available, cannot create windows.
Viewer::realize() - failed to set up any windows.
I build and re-build many times, using CMake with or without Gui, compiling Unix files or from within Xcode, but still same problem.
Thank you!
If you'd like a more recent Mac OSG binary which includes a
user-runnable installer, OSG Frameworks supporting both 32 and 64-bit
archs, etc. you can use the one published by ARToolworks:
http://www.artoolworks.com/dist/openscenegraph/3.1.x/
It doesn't include the COLLADA (.dae) plugin but most other plugins
are present.
Regards, Phil.
It sounds like somehow the GraphicsWindow*.cpp file didn't compile and link and execute, as this is what provides the WindowSystemInterface. This is an unusual condition, as normally this is built automatically, linked in and executed as the library starts up and the user is never the wiser.
I'm not sure what to advise you, only to re-check you build process as something has gone very wrong.