Trouble installing gmp library

If you are using Xcode to compile:

If the header file is in a non-standard place you add the path in the Build Settings section of the project:

But again you need to know where the make install placed the header file first. And if you did not run it sudo did you get any errors?

Thank you Hoffman for your reply.

I went through suggested stackoverflow. However I may need to give more information about what I have done so far. First of all I am using embedxcode installed in xcode 4.6.3. The gmp library installed in /usr/local/cellar/gmp/5.1.3. When I tried to Link binary with libraries I selected index as there is no option for Build phase in the project Tab and this shown in the below picture

Then I added the libgmp.dylib as it can be seen below:

Accrodingly I added the header search path and library search as shown in the picture below

Then i tried to build all but now I am getting different error which says the gmp.h no such file or directory depsite it shows me when I am start call gmp function in the library is reponding as shown below

I hope you can guide me solving this error as I am new to the xcode.

Angle brackets (<>) tell the compiler to look for the header file on the standard search paths for the system. It's unlikely that a library you've built yourself will be installed there. In fact, the normal location for programs built using the "./configure, make, make install" idiom is /usr/local.

Therefore, your headers are most likely in /usr/local/include and the corresponding library in /usr/local/lib. You will need to pass those to the compiler, either in Xcode settings (if using Xcode) or using the -I (capital-I), -L and -l (lower-case L) switches (if using the command line or makefiles). In that case, the proper way to include your header file is using double-quotes (#include "gmp.h")

Passing through the compiler means to compile the code. g_wolfman is referring C and C++ include-file angle-bracket syntax, and how to explicitly tell the compiler where the system (angle-bracket) includes are actually located in the file system, if the files involved are not in the expected location.

To compile C and C++ code on OS X, ensure the command-line tools are enabled within Xcode.app > Preferences > Downloads > Components. This setting causes Xcode to create the traditional commands used to invoke the compilers and the linker, and these commands are what the shell scripts and configure scripts generally expect. Now run those build and configuration scripts again.

If those configuration scripts fail, then you will have to do some work porting gmp to OS X, figuring out what happened with the script. Alternatively, the homebrew tool — a package installer for OS X — can a previously-ported version, and it looks like homebrew does have a recipe for gmp.

Though it's probably a little late for this, it's also good practice to have a backup of your system before starting to work with an open-source configure script, as not all of the scripts will work or will work on OS X, and not all of the scripts will "play nice" with the file system and existing system tools and libraries. Files, libraries and header files can be overwritten by some configure scripts, and that can cause dependent software elsewhere in OS X to fail.

I am trying to use GMP in Xcode I followed the steps below to link the library:

1) Open the left panel, goto "ProjectName", Targets, Build phases, Link binary with libraries and select your library.

2) Open the left panel, goto "ProjectName", Project, Header Search Paths, write the path where the headers of your library are (the .h files, usually in /usr/local/include).

3) Open the left panel, goto "ProjectName", Project, Library Search Paths, write the path where your libraries are (the .a or .dylib files, usually in /usr/local/lib)

but when I am using mpz_init (); function Xcode reported undefined reference to __gmpz_init error any idea on how to resolve this error

OK: so the text that malbahri has posted here appears to be extracted from this StackOverflow question.

I'm assuming you're using some version of Xcode4 or Xcode 5. If so, I'd expect to have to reference the libgmp bits within the Xcode link and search path settings. This is what Frank Caggiano referenced. Here's a longer StackOverflow discussion on this topic, with some more details.

malbahri wrote:

Thank you Hoffman for your reply.

I went through suggested stackoverflow. However I may need to give more information about what I have done so far. First of all I am using embedxcode installed in xcode 4.6.3. The gmp library installed in /usr/local/cellar/gmp/5.1.3. When I tried to Link binary with libraries I selected index as there is no option for Build phase in the project Tab and this shown in the below picture

This is a Makefile-based project. I think you will have to edit the Makefile to add -L/usr/local/cellar/gmp/5.1.3 -lgmp or something like that.

malbahri wrote:

Any idea where I have to add -lgmp ?

I'm sorry, but you've been handed a fairly complicated project. There really isn't enough room here to explain makefiles. Look for the "Makefile" in the project and see where it is looking for gmp.

This is for arduino? Do you really need GMP? If you don't already know your way around Xcode and Makefiles pretty well, I suggest you stick to the Arduino environment. It works fine.

Yes, it is for arduino and I do need GMP and some other third parties library which I am trying to link it to my project but at the first stage I am trying with GMP. In fact, Arduino IDE is not providing library linking functionality in order such libraries and that's why I am using embedxcode.

I looked in the Makefile but I couldn't find any thing related to GMP and here I copied the Makefile

#

# embedXcode

# ----------------------------------

# Embedded Computing on Xcode 4

#

# Copyright © Rei VILO, 2010-2013

# All rights reserved

# http://embedxcode.weebly.com

#

# Last update: Sep 12, 2013 release 105

# Parameters

# ----------------------------------

# Xcode takes BOARD_TAG and BOARD_PORT from the .xcconfig file

# For other IDEs than Xcode,

# BOARD_TAG is required

# If not defined, error BOARD_TAG not defined

#

#BOARD_TAG = mega2560

# BOARD_PORT is optional

# If not defined, BOARD_PORT = /dev/tty.usb* (default)

#

#BOARD_PORT = /dev/tty.usbmodem*

# Xcode takes SKETCHBOOK_DIR from preferences.txt

# If not defined, each IDE has its own SKETCHBOOK_DIR (default)

# To share the same SKETCHBOOK_DIR along all IDEs, define

#

#SKETCHBOOK_DIR =

# SERIAL_BAUDRATE for the serial console, 9600 by default

# Uncomment and specify another speed

#

#SERIAL_BAUDRATE = 19200

# Libraries

# ----------------------------------

# Declare application Arduino/chipKIT/Digispark/Energia/Maple/Teensy/Wiring

# and users libraries used

# Short-listing libraries speeds-up building

# Typing = 0 takes none

# Otherwise, leaving empty considers all (default)

# List Arduino/chipKIT/Energia/Maple/Teensy/Wiring libraries here

#

APP_LIBS_LIST =

# List users libraries here

#

USER_LIBS_LIST =

# List core, application and user libraries to be excluded

# For example, WiFi may crash on Arduino 1.0.2

# For example, Esplora may crash on Arduino 1.0.3

# For example, Firmata may crash on Teensy 3.0

# For example, OneWire may crash on MPIDE 0023

# For example, HardwareSerial may conflict with MarlinSerial

#

EXCLUDE_LIBS = Firmata WiFi Esplora OneWire Robot_Control Robot_Control/utility Robot_Motor

# Manage path with space in the name

#

CURRENT_DIR := $(shell pwd)

CURRENT_DIR := $(shell echo '$(CURRENT_DIR)' | sed 's/ /\\\ /g')

MAKEFILE_PATH = $(CURRENT_DIR)/Makefiles

UTILITIES_PATH = $(CURRENT_DIR)/Utilities

include $(MAKEFILE_PATH)/St

How big do your numbers need to be? long long is pretty big. long double can get big too if you don't mind a loss of percision.

Have you installed Xcode? gmp builds fine for me.

To perform these operations, install Xcode (as etresoft mentions) and then ensure that the command-line tools are enabled within Xcode. (Xcode.app > Preferences > Downloads > Components)

Where did gmp.h get installed to? Did you run the make install as root (sudo)?

Normally the header file would go in /usr/include or /usr/local/include and those paths should be searched normally.