Documentation
I note that the documentation page of the NetSurf site says last updated 2 January 2007. I hope I am not being a nuisance in enquiring whether there is any prospect of the :hover pseudoclass being implemented for the RISC OS version any time soon. It is just that there are so many useful features for web pages, such as tooltips, that can be implemented with it. It would be good to be able to see these on a RISC OS browser. Apologies if I am overlooking more recent information. -- Gavin Wraith (ga...@wra1th.plus.com) Home page: http://www.wra1th.plus.com/
Re: NetSurf on ARM9 Fedora based distribution?
Hi John, Thanks for the answer, maybe not exactly what i hoped for, but I appreciate it nevertheless, Cheers, Karsten On 12/19/2011 13:14, John-Mark Bell wrote: On Sat, 2011-12-17 at 16:35 +0100, Karsten Jeppesen wrote: Hi there, Im new to this project, so bear with me if Im barking up the wrong tree. I have made a Fedora based distribution to an ARM9263 processor including using the rpm package system. My tool chain includes a full gcc4.4.2 cross. Is there any documentation on how to proceed in the porting? I don't think so, no. My first inclination was to export the trunk and then form 2 rpms. NetSurfLib and NetSurf itself. It's not clear why you'd want to install the libraries, but not the browser, unless you're building shared libraries, in which case, a package per library would make more sense. O - thats easy to explain. Netsurf itself will look for libraries and headers (its own or dependencies oc) amongst others, in the root file system (/usr/include, /usr/lib etc) but in a cross compiler that doesnt work that way. So you need to get dependencies compiled first and then installed into the cross compiler before continuing. At the moment I think I will end up with 3 rpms - a commonlib, a lib and netsurf itself. Injecting commonlib into the cross in order to compile lib and so on. However I am hitting a few kinks which I believe is enough to start asking these questions. Amongst others I am hit with the problem that gcc in a full cross will refuse dumping the specs which in turn confuses NetSurfs makefile so it wont find the libnsgif simply because it cant figure out what compiler is in play. This doesn't make much sense to me. NetSurf's buildsystem doesn't use -dumpspecs to identify the compiler, or determine where libraries are installed. It does rely on pkg-config, however, and expects that the environment has been configured to allow pkg-config to find the libraries you have installed. Well - it actually does. In order to determine if it is gcc or some other compiler. Makefile.tools. Grep for dumpspecs and you will see. The buildsystem used for the libraries does use -dumpspecs, but falls back to parsing the output of $(CC) --version if that fails (which it shouldn't, even with a full cross) Shouldn't != doesn't. Gcc 4.4.2 does not. Which kinda sucks, but thats the compiler I am locked too for now. If you have successfully built and installed the libraries into a prefix, then you can build NetSurf as follows: export PKG_CONFIG_PATH=/path/to/install/prefix/lib/pkgconfig: $(PKG_CONFIG_PATH) make TARGET=gtk \ CC=/path/to/cross/bin/gcc \ PREFIX=/path/to/install/prefix He he - have you any idea how problematic libtools and pkgconfig are to dance with in a cross environment? Well - CC always points to the compiler. Which of course contains both the native and cross. I will see if I can get pkgconfig to work, but its really a drag. Consider in a crossbuild that like libtools this program is built and running on the same host but collecting information on the target but is not supposed to target the target rather the host. For this purpose libtool takes the ARCH as option, but as far as I can see no such luck with pkg_config. So: - where to look for a porting procedure? See above. - what libs and parts from the trunk are needed for the netsurf build? Read Docs/BUILDING-GTK in the NetSurf source tree. The PACKAGING-GTK document will probably be of some interest, too. :-( - I may not have expressed myself clearly enough - punching is probably faster. - oo - and remember to state that automake ver 1.1 if you want it to compile. Otherwise you will get some strange errors, NetSurf's buildsystem does not use autotools at all, so I don't understand what it is that requires automake. Somehow its involved or I wouldn't write it. Could be in a prerequisite. When I run such i ackage up I use a virgin install on a virtual machine to make sure I get all the oddities. John-Mark. -- Sincerely, Med venlig hilsen, Karsten Jeppesen, D.D.S, B.Sc.Cs Sønder Alle 16 9500 Hobro Cell,tlf: +45 5192 7753 Webmaster, D.B.F Distrikt NordJylland
Re: Documentation
In article b41bb74452.wra...@wra1th.plus.com, Gavin Wraith ga...@wra1th.plus.com wrote: whether there is any prospect of the :hover pseudoclass being implemented for the RISC OS version any time soon It's unlikely to happen soon. Changes to core functionality, like the layout engine, will affect all front ends; it's not something that would need specific work on the RISC OS front end (or any other). For more detailed info see the new layout engine part of the development plan: http://wiki.netsurf-browser.org/Development_Plan http://wiki.netsurf-browser.org/Layout -- Michael Drake (tlsa) http://www.netsurf-browser.org/
Problem launching NetSurf on RPCEmu/Win7
Im running a copy of RPCEmu originally from one of ROOLs London Show memory sticks on a Windows 7 machine (Dell XPS, 3.4GHz Core i7, 8MB RAM). It runs very well, averaging around 300 MIPS, but I find NetSurf 2.8 for RISC OS (installed from a fresh download) will not launch. Ive updated !Boot and !System, but clicking on the NetSurf icon produces an endlessly cycling hourglass. RPCEmu is not yet bridged to the web, but I assume this isnt necessary in order to use NetSurf as (for example) an HTML viewer? I'm inexperienced with RPCEmu (and Windows 7, for that matter), so apologies in advance if I've overlooked the 'bleedin' obvious'. If anyone can tear themselves away from the festivities long enough to reply I should be most grateful! George --
Re: NetSurf on ARM9 Fedora based distribution?
On Wed, 2011-12-21 at 00:12 +0100, Karsten Jeppesen wrote: On 12/19/2011 13:14, John-Mark Bell wrote: On Sat, 2011-12-17 at 16:35 +0100, Karsten Jeppesen wrote: My first inclination was to export the trunk and then form 2 rpms. NetSurfLib and NetSurf itself. It's not clear why you'd want to install the libraries, but not the browser, unless you're building shared libraries, in which case, a package per library would make more sense. O - thats easy to explain. Netsurf itself will look for libraries and headers (its own or dependencies oc) amongst others, in the root file system (/usr/include, /usr/lib etc) but in a cross compiler that doesnt work that way. It will look in a number of places, depending on the parameters passed to make. As I said before, however, building the GTK frontend is entirely dependent upon pkg-config. So you need to get dependencies compiled first and then installed into the cross compiler before continuing. Yes, and this is what we do for all of the platforms for which we cross-compile NetSurf. At the moment I think I will end up with 3 rpms - a commonlib, a lib and netsurf itself. Injecting commonlib into the cross in order to compile lib and so on. Up to you, I guess. Unless you're intending to ship the libraries, I don't understand why you don't just build them into a prefix, and tell NetSurf's buildsystem to look in there. However I am hitting a few kinks which I believe is enough to start asking these questions. Amongst others I am hit with the problem that gcc in a full cross will refuse dumping the specs which in turn confuses NetSurfs makefile so it wont find the libnsgif simply because it cant figure out what compiler is in play. This doesn't make much sense to me. NetSurf's buildsystem doesn't use -dumpspecs to identify the compiler, or determine where libraries are installed. It does rely on pkg-config, however, and expects that the environment has been configured to allow pkg-config to find the libraries you have installed. Well - it actually does. In order to determine if it is gcc or some other compiler. Makefile.tools. Grep for dumpspecs and you will see. As I said below, this is the buildsystem used for the libraries. NetSurf itself uses a different one. Regardless, please provide full build logs of your progress so far. At present, it's not clear to me that you have built the libraries that NetSurf depends upon, let alone the browser itself. The buildsystem used for the libraries does use -dumpspecs, but falls back to parsing the output of $(CC) --version if that fails (which it shouldn't, even with a full cross) Shouldn't != doesn't. Gcc 4.4.2 does not. Which kinda sucks, but thats the compiler I am locked too for now. Please provide the verbatim output of both gcc -dumpspecs and gcc --version for the toolchain you're using. If you have successfully built and installed the libraries into a prefix, then you can build NetSurf as follows: export PKG_CONFIG_PATH=/path/to/install/prefix/lib/pkgconfig: $(PKG_CONFIG_PATH) make TARGET=gtk \ CC=/path/to/cross/bin/gcc \ PREFIX=/path/to/install/prefix He he - have you any idea how problematic libtools and pkgconfig are to dance with in a cross environment? They really aren't that complex. For pkg-config, export PKG_CONFIG_LIBDIR with the path to your cross environment's lib/pkgconfig directory. Well - CC always points to the compiler. Which of course contains both the native and cross. I don't follow. CC contains the path to the compiler binary, not the bin directory in which the toolchain binaries are stored. I will see if I can get pkgconfig to work, but its really a drag. Consider in a crossbuild that like libtools this program is built and running on the same host but collecting information on the target but is not supposed to target the target rather the host. For this purpose libtool takes the ARCH as option, but as far as I can see no such luck with pkg_config. All pkg-config does is parse text files, so as long as you have a pkg-config binary that runs on the machine on which you're compiling things, it's fine -- just point it at the correct pkgconfig directory, as I describe above. - oo - and remember to state that automake ver 1.1 if you want it to compile. Otherwise you will get some strange errors, NetSurf's buildsystem does not use autotools at all, so I don't understand what it is that requires automake. Somehow its involved or I wouldn't write it. The full build log would help here, too. John-Mark.
FGW web site has gone completely bananas
This has probably got more to do with First Group redesigning their web site than NetSurf, but http://www.firstgreatwestern.co.uk/ fails to render anywhere close to what it should look like. Mind you the home page has 36 validation errors. -- Richard Porterhttp://www.minijem.plus.com/ mailto:r...@minijem.plus.com I don't want a user experience - I just want stuff that works.
Re: Problem launching NetSurf on RPCEmu/Win7
On Wed, 2011-12-21 at 15:18 +, george wrote: I‘m running a copy of RPCEmu originally from one of ROOL‘s London Show memory sticks on a Windows 7 machine (Dell XPS, 3.4GHz Core i7, 8MB RAM). It runs very well, averaging around 300 MIPS, but I find NetSurf 2.8 for RISC OS (installed from a fresh download) will not launch. I‘ve updated !Boot and !System, but clicking on the NetSurf icon produces an endlessly cycling hourglass. RPCEmu is not yet bridged to the web, but I assume this isn‘t necessary in order to use NetSurf as (for example) an HTML viewer? Unfortunately, you've not given us enough to go on to have any chance of helping you. Please provide a log file from an attempt to start NetSurf on your system. Thanks, John-Mark.
Re: Problem launching NetSurf on RPCEmu/Win7
On 21 Dec, John-Mark Bell wrote in message 1324503435.7505.50.camel@duiker: On Wed, 2011-12-21 at 15:18 +, george wrote: I‘m running a copy of RPCEmu originally from one of ROOL‘s London Show memory sticks on a Windows 7 machine (Dell XPS, 3.4GHz Core i7, 8MB RAM). It runs very well, averaging around 300 MIPS, but I find NetSurf 2.8 for RISC OS (installed from a fresh download) will not launch. I‘ve updated !Boot and !System, but clicking on the NetSurf icon produces an endlessly cycling hourglass. RPCEmu is not yet bridged to the web, but I assume this isn‘t necessary in order to use NetSurf as (for example) an HTML viewer? Unfortunately, you've not given us enough to go on to have any chance of helping you. Please provide a log file from an attempt to start NetSurf on your system. Just to remove one possibly clutchable straw, NetSurf (test builds of, at least) runs quite happily under at least some RPCemu setups, whether or not networking is active. The RISC OS front-end gets tested like that quite frequently, so I'd probably notice if it didn't work. So yes, a logfile will be needed. -- Steve Fryatt - Leeds, England Wakefield Acorn RISC OS Show Saturday 28 April 2012 http://www.stevefryatt.org.uk/ http://www.wakefieldshow.org.uk/
