On Darwin (macOS), the flags needed to create a shared
library are different. Moreover, the extension is .dylib
and the version portion of the soname is inserted between
the library name and the libext, e.g. lifoo.1.2.3.dylib.
Signed-off-by: Caleb Xu <calebcenter@live.com>
---
makefiles/Makefile.clang | 7 ++++++-
makefiles/Makefile.gcc | 6 +++++-
makefiles/Makefile.tools | 6 +++++-
makefiles/Makefile.top | 14 +++++++++++---
4 files changed, 27 insertions(+), 6 deletions(-)
diff --git a/makefiles/Makefile.clang b/makefiles/Makefile.clang
index 50f8a82..bcd14e3 100644
--- a/makefiles/Makefile.clang
+++ b/makefiles/Makefile.clang
@@ -21,7 +21,12 @@ CXXSHR := -fPIC
LDDBG := -g
# Reevaluation is required here
-LDSHR = -shared -Wl,-soname,$(SONAME)
+ifeq ($(findstring darwin,$(HOST)),darwin)
+ LDSHR = -dynamiclib -install_name $(SONAME)
+else
+ LDSHR = -shared -Wl,-soname,$(SONAME)
+endif
+
ARFLG := cru
diff --git a/makefiles/Makefile.gcc b/makefiles/Makefile.gcc
index b5119ac..4a9dff7 100644
--- a/makefiles/Makefile.gcc
+++ b/makefiles/Makefile.gcc
@@ -20,7 +20,11 @@ CXXSHR := -fPIC
LDDBG := -g
# Reevaluation is required here
-LDSHR = -shared -Wl,-soname,$(SONAME)
+ifeq ($(findstring darwin,$(HOST)),darwin)
+ LDSHR = -dynamiclib -install_name $(SONAME)
+else
+ LDSHR = -shared -Wl,-soname,$(SONAME)
+endif
ARFLG := cru
diff --git a/makefiles/Makefile.tools b/makefiles/Makefile.tools
index 112e7f8..e5504e7 100644
--- a/makefiles/Makefile.tools
+++ b/makefiles/Makefile.tools
@@ -478,7 +478,11 @@ LDFLAGS := $(LDFLAGS) $(OPTLDFLAGS)
ifeq ($(COMPONENT_TYPE),lib-static)
LIBEXT ?= .a
else
- LIBEXT ?= .so
+ ifeq ($(findstring darwin,$(HOST)),darwin)
+ LIBEXT ?= .dylib
+ else
+ LIBEXT ?= .so
+ endif
endif
# If we're building a shared library, modify the flags appropriately
diff --git a/makefiles/Makefile.top b/makefiles/Makefile.top
index caac166..0b0fe22 100644
--- a/makefiles/Makefile.top
+++ b/makefiles/Makefile.top
@@ -189,9 +189,17 @@ endif
# Determine the output filename
ifeq ($(findstring lib,$(COMPONENT_TYPE)),lib)
ifeq ($(findstring lib-shared,$(COMPONENT_TYPE)),lib-shared)
- SHAREDLIBNAME := lib$(COMPONENT)$(LIBEXT)
- SONAME := $(SHAREDLIBNAME).$(major-version)
- OUTPUT := $(BUILDDIR)/$(SHAREDLIBNAME).$(COMPONENT_VERSION)
+ ifeq ($(findstring darwin,$(HOST)),darwin)
+ # In macOS, shared lib filenames are of the form libfoo.dylib,
+ # libfoo.1.dylib, or libfoo.1.2.3.dylib
+ SONAME := lib$(COMPONENT).$(major-version)$(LIBEXT)
+ SHAREDLIBNAME := lib$(COMPONENT)$(LIBEXT)
+ OUTPUT := $(BUILDDIR)/lib$(COMPONENT).$(COMPONENT_VERSION)$(LIBEXT)
+ else
+ SHAREDLIBNAME := lib$(COMPONENT)$(LIBEXT)
+ SONAME := $(SHAREDLIBNAME).$(major-version)
+ OUTPUT := $(BUILDDIR)/$(SHAREDLIBNAME).$(COMPONENT_VERSION)
+ endif
else
OUTPUT := $(BUILDDIR)/lib$(COMPONENT)$(LIBEXT)
endif
--
2.41.0
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Friday, 30 June 2023
Tuesday, 27 June 2023
Re: Netsurf versions
In article <5abb26f5a7netsurf@avisoft.f9.co.uk>,
Martin Avison <netsurf@avisoft.f9.co.uk> wrote:
> The numbers will be muddled, as with any list of files the file names
> are the sequence, and the number is a minor part of the filename. It
> seems that the naming convention before the number has changed. There
> even seem to be two 5433 files -
> https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-riscos-gnueabi-gcc-5433.zip
> https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-unknown-riscos-gcc-5433.zip
> I have no idea what the difference is!
The toolchain. The first one is built with the new one and the second
one with the old.
Regards,
--
Frank
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Martin Avison <netsurf@avisoft.f9.co.uk> wrote:
> The numbers will be muddled, as with any list of files the file names
> are the sequence, and the number is a minor part of the filename. It
> seems that the naming convention before the number has changed. There
> even seem to be two 5433 files -
> https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-riscos-gnueabi-gcc-5433.zip
> https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-unknown-riscos-gcc-5433.zip
> I have no idea what the difference is!
The toolchain. The first one is built with the new one and the second
one with the old.
Regards,
--
Frank
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: Netsurf versions
In article <5abb231a1bmec@npost.uk>,
Chris Newman <mec@npost.uk> wrote:
> In article <f4091bbb5a.DBarrass@DB>, DB <d.barrass@zoho.eu> wrote:
> > Perhaps the announcement by Michael Drake about a new toolchain
> > (https://www.riscosopen.org/forum/forums/1/topics/17766) is the
> > explanation.
> > Using Frank de Bruijn's latest version of Fetch_NS (2.50
> > 17-03-2023) allows the user to select those versions built with
> > the new toolchain by setting "Set Fetch_NS$NewToolchain 1"
> > (without the quotes) in the settings file.
> The new toolchain version I downloaded has nothing on the icon bar
> menu to distiguish it from the other flavour.
> Using the link within the above topics link thus
> https://ci.netsurf-browser.org/builds/riscos/?C=M;O=D
> I see the list of builds but as folk have noticed, the number order
> is muddled.
The numbers will be muddled, as with any list of files the file names
are the sequence, and the number is a minor part of the filename. It
seems that the naming convention before the number has changed. There
even seem to be two 5433 files -
https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-riscos-gnueabi-gcc-5433.zip
https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-unknown-riscos-gcc-5433.zip
I have no idea what the difference is!
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Chris Newman <mec@npost.uk> wrote:
> In article <f4091bbb5a.DBarrass@DB>, DB <d.barrass@zoho.eu> wrote:
> > Perhaps the announcement by Michael Drake about a new toolchain
> > (https://www.riscosopen.org/forum/forums/1/topics/17766) is the
> > explanation.
> > Using Frank de Bruijn's latest version of Fetch_NS (2.50
> > 17-03-2023) allows the user to select those versions built with
> > the new toolchain by setting "Set Fetch_NS$NewToolchain 1"
> > (without the quotes) in the settings file.
> The new toolchain version I downloaded has nothing on the icon bar
> menu to distiguish it from the other flavour.
> Using the link within the above topics link thus
> https://ci.netsurf-browser.org/builds/riscos/?C=M;O=D
> I see the list of builds but as folk have noticed, the number order
> is muddled.
The numbers will be muddled, as with any list of files the file names
are the sequence, and the number is a minor part of the filename. It
seems that the naming convention before the number has changed. There
even seem to be two 5433 files -
https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-riscos-gnueabi-gcc-5433.zip
https://ci.netsurf-browser.org/builds/riscos/NetSurf-arm-unknown-riscos-gcc-5433.zip
I have no idea what the difference is!
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: Netsurf versions
In article <f4091bbb5a.DBarrass@DB>, DB <d.barrass@zoho.eu> wrote:
> In message <5abaa82a53mec@npost.uk> Chris Newman <mec@npost.uk> wrote:
> > Hi,
> > If I use !Fetch_NS I get version Dev C1# 5433.
> > If I go through the Download latest NetSurf fro th browser itself I
> > get version Dev C1# 5415.
> > Would someone kindly explain?
> Perhaps the announcement by Michael Drake about a new toolchain
> (https://www.riscosopen.org/forum/forums/1/topics/17766) is the
> explanation.
> Using Frank de Bruijn's latest version of Fetch_NS (2.50 17-03-2023)
> allows the user to select those versions built with the new toolchain
> by setting "Set Fetch_NS$NewToolchain 1" (without the quotes) in the
> settings file.
The new toolchain version I downloaded has nothing on the icon bar menu
to distiguish it from the other flavour.
Using the link within the above topics link thus
https://ci.netsurf-browser.org/builds/riscos/?C=M;O=D
I see the list of builds but as folk have noticed, the number order is
muddled.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> In message <5abaa82a53mec@npost.uk> Chris Newman <mec@npost.uk> wrote:
> > Hi,
> > If I use !Fetch_NS I get version Dev C1# 5433.
> > If I go through the Download latest NetSurf fro th browser itself I
> > get version Dev C1# 5415.
> > Would someone kindly explain?
> Perhaps the announcement by Michael Drake about a new toolchain
> (https://www.riscosopen.org/forum/forums/1/topics/17766) is the
> explanation.
> Using Frank de Bruijn's latest version of Fetch_NS (2.50 17-03-2023)
> allows the user to select those versions built with the new toolchain
> by setting "Set Fetch_NS$NewToolchain 1" (without the quotes) in the
> settings file.
The new toolchain version I downloaded has nothing on the icon bar menu
to distiguish it from the other flavour.
Using the link within the above topics link thus
https://ci.netsurf-browser.org/builds/riscos/?C=M;O=D
I see the list of builds but as folk have noticed, the number order is
muddled.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: Netsurf versions
In message <5abaa82a53mec@npost.uk>
Chris Newman <mec@npost.uk> wrote:
> Hi,
> If I use !Fetch_NS I get version Dev C1# 5433.
> If I go through the Download latest NetSurf fro th browser itself I get
> version Dev C1# 5415.
> Would someone kindly explain?
Perhaps the announcement by Michael Drake about a new toolchain
(https://www.riscosopen.org/forum/forums/1/topics/17766) is the
explanation.
Using Frank de Bruijn's latest version of Fetch_NS (2.50 17-03-2023)
allows the user to select those versions built with the new toolchain by
setting "Set Fetch_NS$NewToolchain 1" (without the quotes) in the settings
file.
Dave
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Chris Newman <mec@npost.uk> wrote:
> Hi,
> If I use !Fetch_NS I get version Dev C1# 5433.
> If I go through the Download latest NetSurf fro th browser itself I get
> version Dev C1# 5415.
> Would someone kindly explain?
Perhaps the announcement by Michael Drake about a new toolchain
(https://www.riscosopen.org/forum/forums/1/topics/17766) is the
explanation.
Using Frank de Bruijn's latest version of Fetch_NS (2.50 17-03-2023)
allows the user to select those versions built with the new toolchain by
setting "Set Fetch_NS$NewToolchain 1" (without the quotes) in the settings
file.
Dave
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: Netsurf versions
On 27 Jun 2023 Dave wrote:
> In article <adebbbba5a.ricp@user.minijem.plus.com>,
> Richard Porter <ricp@minijem.plus.com> wrote:
>> On 26 Jun 2023 Chris Newman wrote:
>>> If I use !Fetch_NS I get version Dev C1# 5433.
>>> If I go through the Download latest NetSurf fro th browser itself I
>>> get version Dev C1# 5415.
>>> Would someone kindly explain?
>> I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
>> as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
>> sight at the top of the list. I'd never thought of looking there.
>> Richard
> Interesting...
> On the list as displayed here by Netsurf, from the above noted URL, 5433
> is 30 items down the list, not at the top.
Yes but 5415 to 5433 are, as a block, at the top. That leaves 5433 in the
middle of the whole list.
--
Richard Porter
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> In article <adebbbba5a.ricp@user.minijem.plus.com>,
> Richard Porter <ricp@minijem.plus.com> wrote:
>> On 26 Jun 2023 Chris Newman wrote:
>>> If I use !Fetch_NS I get version Dev C1# 5433.
>>> If I go through the Download latest NetSurf fro th browser itself I
>>> get version Dev C1# 5415.
>>> Would someone kindly explain?
>> I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
>> as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
>> sight at the top of the list. I'd never thought of looking there.
>> Richard
> Interesting...
> On the list as displayed here by Netsurf, from the above noted URL, 5433
> is 30 items down the list, not at the top.
Yes but 5415 to 5433 are, as a block, at the top. That leaves 5433 in the
middle of the whole list.
--
Richard Porter
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Monday, 26 June 2023
Re: Netsurf versions
In article <adebbbba5a.ricp@user.minijem.plus.com>,
Richard Porter <ricp@minijem.plus.com> wrote:
> On 26 Jun 2023 Chris Newman wrote:
> > If I use !Fetch_NS I get version Dev C1# 5433.
> > If I go through the Download latest NetSurf fro th browser itself I
> > get version Dev C1# 5415.
> > Would someone kindly explain?
> I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
> as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
> sight at the top of the list. I'd never thought of looking there.
> Richard
Interesting...
On the list as displayed here by Netsurf, from the above noted URL, 5433
is 30 items down the list, not at the top.
Dave
--
Dave Triffid
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Richard Porter <ricp@minijem.plus.com> wrote:
> On 26 Jun 2023 Chris Newman wrote:
> > If I use !Fetch_NS I get version Dev C1# 5433.
> > If I go through the Download latest NetSurf fro th browser itself I
> > get version Dev C1# 5415.
> > Would someone kindly explain?
> I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
> as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
> sight at the top of the list. I'd never thought of looking there.
> Richard
Interesting...
On the list as displayed here by Netsurf, from the above noted URL, 5433
is 30 items down the list, not at the top.
Dave
--
Dave Triffid
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: Netsurf versions
On 26 Jun 2023 Chris Newman wrote:
> If I use !Fetch_NS I get version Dev C1# 5433.
> If I go through the Download latest NetSurf fro th browser itself I get
> version Dev C1# 5415.
> Would someone kindly explain?
I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
sight at the top of the list. I'd never thought of looking there.
Richard
--
Richard Porter https://www.minijem.plus.com
t: @westernexplorer mailto:ricp@minijem.plus.com
Sent from my ... if you really want to know look at the headers.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> If I use !Fetch_NS I get version Dev C1# 5433.
> If I go through the Download latest NetSurf fro th browser itself I get
> version Dev C1# 5415.
> Would someone kindly explain?
I use https://ci.netsurf-browser.org/builds/riscos/ and that goes as far
as 5414. I've just noticed that 5415 to 5433 are hidden away in clear
sight at the top of the list. I'd never thought of looking there.
Richard
--
Richard Porter https://www.minijem.plus.com
t: @westernexplorer mailto:ricp@minijem.plus.com
Sent from my ... if you really want to know look at the headers.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Netsurf versions
Hi,
If I use !Fetch_NS I get version Dev C1# 5433.
If I go through the Download latest NetSurf fro th browser itself I get
version Dev C1# 5415.
Would someone kindly explain?
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
If I use !Fetch_NS I get version Dev C1# 5433.
If I go through the Download latest NetSurf fro th browser itself I get
version Dev C1# 5415.
Would someone kindly explain?
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Saturday, 24 June 2023
[gccsdk] Hatari (vfp) 2.3.1-1 on riscos.info audio thread fails to initialise
To whom it may concern,
Theo Markettos suggested I post a bug report here with regard to the
hatari (vfp) 2.3.1-1 package on riscos.info.
It started with The Bard's Tale (TBT). That game consumed an Atari ST and
months of my life many decades ago. So when I discovered the build of
Hatari (vfp) 2.3.1-1 available on riscos.info, in a fit of nostalgia I
attempted to play TBT with it. However, it does not play audio. Music (of
sorts) is an integral part of TBT gameplay. The fault appears to lie
within the linked-in (customised?) build of the SDL library. Hatari's
audio thread failed to initialise. I didn't dig deeper into the binary to
try to figure out why. I was able to rebuild Hatari 2.3.1 from source
without too much trouble. I then found that audio worked as expected. So
if a customised version of SDL was indeed used, I suggest that the hatari
package on riscos.info be rebuilt and tested using the default GCCSDK
packages. I have no idea whose very-low-priority job that would be. It is
likely I'm the only person who cared, and I don't any more because my own
build works well enough. If it is nobody's job, then I'd consider making
it my job if someone could outline how I'd make it my job... if someone
cares.
--
Regards,
Christopher Martin
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Theo Markettos suggested I post a bug report here with regard to the
hatari (vfp) 2.3.1-1 package on riscos.info.
It started with The Bard's Tale (TBT). That game consumed an Atari ST and
months of my life many decades ago. So when I discovered the build of
Hatari (vfp) 2.3.1-1 available on riscos.info, in a fit of nostalgia I
attempted to play TBT with it. However, it does not play audio. Music (of
sorts) is an integral part of TBT gameplay. The fault appears to lie
within the linked-in (customised?) build of the SDL library. Hatari's
audio thread failed to initialise. I didn't dig deeper into the binary to
try to figure out why. I was able to rebuild Hatari 2.3.1 from source
without too much trouble. I then found that audio worked as expected. So
if a customised version of SDL was indeed used, I suggest that the hatari
package on riscos.info be rebuilt and tested using the default GCCSDK
packages. I have no idea whose very-low-priority job that would be. It is
likely I'm the only person who cared, and I don't any more because my own
build works well enough. If it is nobody's job, then I'd consider making
it my job if someone could outline how I'd make it my job... if someone
cares.
--
Regards,
Christopher Martin
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Monday, 19 June 2023
Re: User Agent
On Mon, Jun 19, 2023 at 11:55:35AM +0300, jtzz11@post.com wrote:
> What does "--url_file" do? will NS load all urls listed there?
It controls where the URL database is stored, ie history etc. It does
not do what you want.
We should probably provide a way to define more than one home page in
preferences to open multiple windows/tabs, but this may end up being
front-end specific rather than in the core.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> What does "--url_file" do? will NS load all urls listed there?
It controls where the URL database is stored, ie history etc. It does
not do what you want.
We should probably provide a way to define more than one home page in
preferences to open multiple windows/tabs, but this may end up being
front-end specific rather than in the core.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: User Agent
Thanks.
What does "--url_file" do? will NS load all urls listed there? .
Regards
On 19/6/23 11:26, Rob Kendrick wrote:
What does "--url_file" do? will NS load all urls listed there? .
Regards
On 19/6/23 11:26, Rob Kendrick wrote:
That suggests no, then. B.
Re: User Agent
On Mon, Jun 19, 2023 at 11:21:21AM +0300, jtzz11@post.com wrote:
> Thanks.
> Can the gtk version accept multiple urls on the commandline?.
>
> The man pages shows "netsurf [options] [url]" (i.e., a single url) &
> issuing "netsurf-gtk www.yahoo.com www.google.com" starts with a
> single tab (yahoo).
That suggests no, then.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> Thanks.
> Can the gtk version accept multiple urls on the commandline?.
>
> The man pages shows "netsurf [options] [url]" (i.e., a single url) &
> issuing "netsurf-gtk www.yahoo.com www.google.com" starts with a
> single tab (yahoo).
That suggests no, then.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: User Agent
Thanks.
Can the gtk version accept multiple urls on the commandline?.
The man pages shows "netsurf [options] [url]" (i.e., a single url) &
issuing "netsurf-gtk www.yahoo.com www.google.com" starts with a single
tab (yahoo).
Thanks
On 19/6/23 11:04, Rob Kendrick wrote:
>
> It depends on the frontend in use. I know the Gtk front end does, and I
> know the RISC OS one does not. As for the others, I am uncertain.
>
> B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Can the gtk version accept multiple urls on the commandline?.
The man pages shows "netsurf [options] [url]" (i.e., a single url) &
issuing "netsurf-gtk www.yahoo.com www.google.com" starts with a single
tab (yahoo).
Thanks
On 19/6/23 11:04, Rob Kendrick wrote:
>
> It depends on the frontend in use. I know the Gtk front end does, and I
> know the RISC OS one does not. As for the others, I am uncertain.
>
> B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: User Agent
On Mon, Jun 19, 2023 at 10:50:52AM +0300, jtzz11@post.com wrote:
> Thanks Rob for the prompt reply.
>
> Another question please - are tabs supported?.
It depends on the frontend in use. I know the Gtk front end does, and I
know the RISC OS one does not. As for the others, I am uncertain.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
> Thanks Rob for the prompt reply.
>
> Another question please - are tabs supported?.
It depends on the frontend in use. I know the Gtk front end does, and I
know the RISC OS one does not. As for the others, I am uncertain.
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: User Agent
Thanks Rob for the prompt reply.
Another question please - are tabs supported?.
Regards
On 19/6/23 10:47, Rob Kendrick wrote:
> On Mon, Jun 19, 2023 at 10:17:41AM +0300, Joel T. wrote:
>> Hi,
>>
>> Can the User Agent string be set, e.g. as in Elinks?.
> Not without recompiling it, see utils/useragent.c
>
> B.
> _______________________________________________
> netsurf-users mailing list -- netsurf-users@netsurf-browser.org
> To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Another question please - are tabs supported?.
Regards
On 19/6/23 10:47, Rob Kendrick wrote:
> On Mon, Jun 19, 2023 at 10:17:41AM +0300, Joel T. wrote:
>> Hi,
>>
>> Can the User Agent string be set, e.g. as in Elinks?.
> Not without recompiling it, see utils/useragent.c
>
> B.
> _______________________________________________
> netsurf-users mailing list -- netsurf-users@netsurf-browser.org
> To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: User Agent
On Mon, Jun 19, 2023 at 10:17:41AM +0300, Joel T. wrote:
>
> Hi,
>
> Can the User Agent string be set, e.g. as in Elinks?.
Not without recompiling it, see utils/useragent.c
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
>
> Hi,
>
> Can the User Agent string be set, e.g. as in Elinks?.
Not without recompiling it, see utils/useragent.c
B.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
User Agent
Hi,
Can the User Agent string be set, e.g. as in Elinks?.
Thanks
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Can the User Agent string be set, e.g. as in Elinks?.
Thanks
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Sunday, 18 June 2023
Re: netsurf-users Digest, Vol 180, Issue 3
On 18 Jun 2023 as I do recall,
pslegg@scubadivers.co.uk wrote:
> Is the list working again ?
>
> I haven't been able to post to it for months.
>
Appears to be working from this end.
--
Harriet Bazley == Loyaulte me lie ==
Sattinger's Law: It works better if you plug it in.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
pslegg@scubadivers.co.uk wrote:
> Is the list working again ?
>
> I haven't been able to post to it for months.
>
Appears to be working from this end.
--
Harriet Bazley == Loyaulte me lie ==
Sattinger's Law: It works better if you plug it in.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Re: netsurf-users Digest, Vol 180, Issue 3
Is the list working again ?
I haven't been able to post to it for months.
Peter
On 18 Jun 2023, at 00:00, netsurf-users-request@netsurf-browser.org wrote:
Send netsurf-users mailing list submissions to
netsurf-users@netsurf-browser.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
netsurf-users-request@netsurf-browser.org
You can reach the person managing the list at
netsurf-users-owner@netsurf-browser.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netsurf-users digest..."
Today's Topics:
1. User Agent (jtzz11@post.com)
Date: Sat, 17 Jun 2023 10:50:54 +0300
From: "jtzz11@post.com" <jtzz11@post.com>
Subject: User Agent
To: netsurf-users@netsurf-browser.org
Message-ID: <10c15b4c-fc8c-8b8c-7fb2-96954edbf75a@post.com>
Content-Type: text/html; charset=UTF-8
<html style="direction: ltr;">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body bidimailui-charset-is-forced="true" style="direction: ltr;">
<p><font face="DejaVu Sans">Hi,</font></p>
<p><br>
</p>
<p><font face="DejaVu Sans">A new NS user here.</font></p>
<p><font face="DejaVu Sans">Can the User Agent string be set, e.g.
as in Elinks?.</font></p>
<p><br>
</p>
<p><font face="DejaVu Sans">Thanks</font><br>
</p>
</body>
</html>
Subject: Digest Footer
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
End of netsurf-users Digest, Vol 180, Issue 3
*********************************************
Saturday, 17 June 2023
Wednesday, 14 June 2023
Portability patches to libcss libdom libutf8proc netsurf
Hello, as communicated on IRC, these attached patches replace
instances of int with int32_t where necessary to compile on platforms
where int32_t is actually long, alongside using the portable format
macros (e.g. PRIx32 where x or lx can't be hardcoded).
Tested by compiling on gcc 13.
Hope this helps, and let me know if I left any of my porting patches
in there instead of just correctness changes!
instances of int with int32_t where necessary to compile on platforms
where int32_t is actually long, alongside using the portable format
macros (e.g. PRIx32 where x or lx can't be hardcoded).
Tested by compiling on gcc 13.
Hope this helps, and let me know if I left any of my porting patches
in there instead of just correctness changes!
Subscribe to:
Posts (Atom)