Re: getting gnustep to work
Success. Finally got the Windows version working. As suggested, I used the Msys shell - but this time when trying to source the file, i used . GNUstep/System/Library/Makefiles/GNUstep.sh instead of . Users/myname/GNUstep/GNUstep/System/Library/Makefiles/GNUstep.sh. I had not allowed for the way the shell maps the directories. Gnustep is actually installed to c:/Users/myname/GNUstep but apparently the shell knows this is the root so it should not be entered. I had not realised that. The GNUstep.sh file is actually in c:\users\myname\GNUstep\GNUstep\System\Library\Makefiles directory. Nearly all the attempts I made previously was from a standard Windows command shell, where the proper full path had to be entered. Also, previously i installed to C:\GNUstep rather than c:\users\myname\GNUstep. I changed to the users directory as I have better permissions to this directory, just in case the problem I was having was permissions related. I did also this time notice the information re sourcing the GNUstep.sh file - it is in the manual.pdf file in the part that describes how to write a first simple program, not with the installation instructions, which probably explains why I did not notice it when I did the install. Anyway, that's my excuse and i'm sticking with it. Anyway, thank you to all those who offered their help. No doubt I will need more before the week is out. -- View this message in context: http://old.nabble.com/getting-gnustep-to-work-tp29673384p29706185.html Sent from the GNUstep - General mailing list archive at Nabble.com. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
simple make file
I have the following simple makefile, copied from the GNUstep manual.pdf, for the simple example program, as follows: include $(GNUSTEP_MAKEFILES)/common.make TOOL_NAME = source.m rabbitMP_OBJC_FILES = source.m include $(GNUSTEP_MAKEFILES)/tool.make Now I want to expand it to incorporate the sqlite3 database, which is in the form of a single source file called sqlite3.c and its accompanying header file sqlite3.h. Somehow the sqlite3 c file needs to be compiled to a linkable static object file and then linked in with the source.m file, which I will modify to include all my new code. I have looked at the documentation for make in the manual.pdf file that comes with Gnustep, but I find it rather incomplete and somewhat incomprehensible. Alternatively if someone could show me how to do it manually from the command line without a make file, that would be good too. Any help would be much appreciated. -- View this message in context: http://old.nabble.com/simple-make-file-tp29707615p29707615.html Sent from the GNUstep - General mailing list archive at Nabble.com. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: simple make file
Richard Frith-Macdonald-2 wrote: For simple database access I'd recommend using the SQLClient package (of course I would since I wrote it) for ease of integration with ObjC ... but using sqlite directly is also quite easy. Since any C source code is also ObjC source code (as C is a subset of ObjC) , you can simply add C files to the list of OBJC source code command ... include $(GNUSTEP_MAKEFILES)/common.make TOOL_NAME = rabbit rabbit_OBJC_FILES = source.m sqlite3.c include $(GNUSTEP_MAKEFILES)/tool.make Adding sqlite3.c to the _OBJC_FILES directive was the first thing I tried. The subsequent make returns make [3]: *** No rule to make target 'obj/rabbit.obj/sqlite3.c', needed by 'obj/rabbit.exe'. Stop.. Using your SQLClient package sounds like the best option in the long term, but I am afraid it might be opening another can of worms. e.g. Where do i get it, how is it installed, etc. Bearing in mind how ignorant I am of C, Obj-C, makefiles, etc. Perhaps I should stick with the static link for now. If you want to give me directions on how to get the package and install it - fine - and if I feel up to it I will give it a go. It would be nice to use proper object based code to access sqlite3. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep -- View this message in context: http://old.nabble.com/simple-make-file-tp29707615p29713961.html Sent from the GNUstep - General mailing list archive at Nabble.com. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: getting gnustep to work
Riccardo Mottola-4 wrote: Hi, Over the years I have tried many times to install and get Gnustep to work. Never had any luck so far. All its ever produced for me is a nice list of error messages. Tried again recently on Windows, no luck. So I tried just now on a clean install of Ubuntu. I installed Gnustep, followed the mini tutorial to create a tiny program and its makefile (below). I then, as instructed, typed make, and as usual, got some error messages (just below). sorry to be sarcastic, but in so many attempts, did you ever read a bit in the wiki or checked the examples provided? The simplest thing you can do is to use ProjectCenter: use tool for a command-line application, type your code and hit build. PC will generate the files for you and run everything for you. Then gradually you can understand what is done automatically for you and tamper yourself. Riccardo That did'nt sound very sarcastic to me - in any case, i'm all growed up now and can handle a moderate amount of sarcasm - I'm quite good at it myself! I have never liked reading documentation much so I tend to avoid doing so whenever possible. In particular I am used to the modern kind of automated installations typical of Windows where the installer does more or less everything for you - which is what I have come to expect (on Windows that is). Nevertheless, I did actually read the info on the web site about installing the system on Microsoft Windows (http://www.gnustep.org/experience/Windows.html), and did as instructed. There is no mention on this page of any kind of post-install procedures, such as sourcing GNUstep.sh, or anything else. Its true I did not trawl through the entire site looking for some additional instructions, but I had no reason to imagine I would need to. As I have already mentioned, since this was a Windows install, I did not expect to have to do anything else beyond the initial mouse click. Indeed I was quite dismayed to find a three-step process - normally you would expect a single stage install, with the installer asking you what components to select (development tools, etc) rather than having a separate install procedure for some additional components. However even I can handle that level of complexity (just). I still cannot really understand why there needs to be any post-install procedures with a Windows install at least. Why can't it be automated? Why can't the installer source the GNUstep.sh? If I can do it manually in such a simple fashion, then surely it can be automated. There are so few versions of Windows compared to the thousands of versions of Linux. Everything is more or less the same from one Windows to the next (directory structure, etc). I don't wish to be known as a whinger, but I have not this kind of problem with any other system. For example, the Vala C-with-objects compiler installed in a single click and worked first time. So too with Ruby, Python, Pike, Lua, Freebasic, Tcl/TK, Clisp, Scheme, Logo, Squeak, etc. These are all developer tools too so are targeting people with good computer skills (perhaps less so with languages like Python), but they have still been given fully automated installations. I'd imagine that had I been able to get Gnustep running those several years ago when I first tried it, that I would not have looked at any other language since. It has always seemed to me to be the best language concept I have seen so far. If only I could have gotten it working. Very likely even I could have got it working eventually if I had been prepared to trawl the forums and the web site documentation, and put lots of man hours of work into solving the many problems, but since I did not know if I would like the language, and because of my intense dislike of forums and searching through doco, I decided instead to go with other languages that did not require so much effort to install. Just my bad luck I guess. Finally, none of this matters when compared to the fact that after following the GNUstep install instructions, and those suggested by people on this forum (sourcing GNUstep.sh, etc), I still cannot get the simplest hello world program to compile on Windows, much less run. Somewhat ironically, the only working Gnustep system I have is on Ubuntu Linux, and it was installed from Ubuntu packages - a simple one click install. In this instance, Ubuntu is more Windows like than Windows. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep -- View this message in context: http://old.nabble.com/getting-gnustep-to-work-tp29673384p29703730.html Sent from the GNUstep - General mailing list archive at Nabble.com. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: getting gnustep to work
Richard Frith-Macdonald-2 wrote: On 10 Sep 2010, at 04:24, stolennomenclature wrote: Over the years I have tried many times to install and get Gnustep to work. Never had any luck so far. All its ever produced for me is a nice list of error messages. Tried again recently on Windows, no luck. So I tried just now on a clean install of Ubuntu. I installed Gnustep, followed the mini tutorial to create a tiny program and its makefile (below). I then, as instructed, typed make, and as usual, got some error messages (just below). First I would like to ask if anyone can help me solve this problem? Second I would like to ask if anyone knows why the developers are able to write such a complex piece of code (gnustep and all its sophisticated libraries) and yet seem unable to write a simple and effective means of installing it? What do you mean by 'installed Gnustep' here? Do you mean that you used Ubuntu packages ... if so then any problem is with the Ubuntu packages rather than anything to do with GNUstep development, and you need to contact the person who is responsible for Ubuntu packages. Of course the packages may have set everything up for you and perhaps all you need to do is log out and log in again ... but if so then perhaps you could ask the package maintainer to have the installation process end with a message to tell you that. On the other hand, it you installed GNUstep stuff by building from source, then you probably forgot to read the installation instructions, README, INSTALL, or any of the installation tutorials available on the net... When you configure gnustep-make there are two main options for the way you install: 1. Install in locations like OpenStep/Apple (unfortunately this is the default for historical reasons) 2. Install in some other location (eg the Linux Filesystem Hierarchy Standard 'configure --with-layout-fhs') If you are installing in the OpenStep/Apple locations then you need environment variables set up to say where to find things ... and all the documentation tells you about this. Basically you need to source GNUstep.sh after installing gnustep-make and every time you log in. If you are installing in a 'native' layout (fhs is probably ok for most linux systems) then things will be where the system expects to find them anyway, and you should not nod to source GNUstep.sh Anyway, once gnustep-make is properly installed, the installation process for any other part of GNUstep is simply 'make install' Yes I used the Ubuntu packages for the Linux, and so is not Gnusteps fault. I have tried installing GNUstep before from source, and indeed lots of other packages, but have never got anything to work. Always lots of incomprehensible error messages, and little else. I am no Linux expert - i am used to Windows, where most install are just one click and it works (well not all the time of course - these are computers after all!). I did use downloaded binary packages from Gnustep for the Windows installation, but that does not work either. I can't quite remember exactly what happened, but it was what prompted me to try installing on Linux. If I feel expecially brave in the morning, I may try a source code install, but if my luck runs true to form, there is little chance it will work. Fingers crossed! ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep -- View this message in context: http://old.nabble.com/getting-gnustep-to-work-tp29673384p29677207.html Sent from the GNUstep - General mailing list archive at Nabble.com. ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
getting gnustep to work
Over the years I have tried many times to install and get Gnustep to work.
Never had any luck so far. All its ever produced for me is a nice list of
error messages. Tried again recently on Windows, no luck. So I tried just
now on a clean install of Ubuntu. I installed Gnustep, followed the mini
tutorial to create a tiny program and its makefile (below). I then, as
instructed, typed make, and as usual, got some error messages (just
below).
First I would like to ask if anyone can help me solve this problem?
Second I would like to ask if anyone knows why the developers are able to
write such a complex piece of code (gnustep and all its sophisticated
libraries) and yet seem unable to write a simple and effective means of
installing it?
Thanks in advance for any help that can be offered.
ERRORS:
make
GNUmakefile:1: /common.make: No such file or directory
GNUmakefile:6: /tool.make: No such file or directory
make: *** No rule to make target `/tool.make'. Stop.
PROGRAM (source.m):
#import Foundation/Foundation.h
int
main (void)
{
NSLog (@Executing);
return 0;
}
MAKEFILE (GNUmakefile):
#import Foundation/Foundation.h
int
main (void)
{
NSLog (@Executing);
return 0;
}
--
View this message in context:
http://old.nabble.com/getting-gnustep-to-work-tp29673384p29673384.html
Sent from the GNUstep - General mailing list archive at Nabble.com.
___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
projectcenter on debian etch wont run - newbie
Trying to start ProjectCenter, I get: [EMAIL PROTECTED]:~$ ProjectCenter /usr/lib/GNUstep/System/Applications/ProjectCenter.app/ProjectCenter: symbol lookup error: /usr/lib/GNUstep/System/Library/Bundles/libgnustep-back.bundle/./libgnustep-back: undefined symbol: FTC_Manager_LookupSize [EMAIL PROTECTED]:~$ I have installed a brand new Debian Etch (Testing) distro, the installed GnuStep as recommended on your web page thus: To perform an installation of all GNUstep packages available under Debian, run apt-get install gnustep gnustep-devel gnustep-games. These packages are currently only available under Debian testing and Unstable (sid). I should have thought following the web guidelines should have resulted in a Gnustep that would at least load ProjectCenter. Anyone any idea why this bog standard install should fail? I have also tried to run Gnustep from a Debian Sarge install. I was able to run ProjectCenter, although with frequent minor bugs manifesting themselves. I successfully created a basic Application type project, which built ok, but when run came up with an error relating to nib files. Also was unable to launch Gorm without an error (dont have access to the exact error text at this time). All in all never been able to run Gnustep at any time. Can anyone help? ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
