Hello!
Its Ahmet Goksu, last years GSoC contributor on ftbench.
This year, I will be contributing development graphics backend natively on
macOS without X11.
Its so exciting to be here again!
here are my infos to connect:
https://www.linkedin.com/in/ahmetgoksu/
https://github.com/goeksu
The Autoconf-generated configure script, or even CMake, respect SHELL, so if a
user gives it a problematic shell, they won't be able to build anything abd
many programs will crash.
But please consider the scenario mentioned before: when a user doesn't have
root permissions to change
Hi again,
I was able to find a cleaner hack by running this command before the
'./configure' script:
export GNUMAKE="make SHELL=$SHELL"
Afterwards, FreeType successfully ran with my desired shell.
But generally, it would greatly help those building FreeType from source
if the configure
Dear Freetype developers,
I was trying to build FreeType from source and noticed that the
'./configure' script does not account for the 'SHELL' environment and
will always use '/bin/sh'.
Looking at the source of the './configure' script, I was able to fix the
problem by manually adding a
There's no guarantee that the user's shell is sh-compatible. autoconf
really means sh here, because that's the shell the script is written for.
Just symlink your favorite shell to sh then, if it's compatible.
behdad
http://behdad.org/
On Wed, May 1, 2024 at 2:13 PM Mohammad Akhlaghi
wrote:
>
I'm not talking about the user overriding the shell specifically. I'm
talking about users who genuinely use a non-POSIX shell as their terminal
shell. Then just running ./configure would fail if configure was to respect
$SHELL.
Or rather you're saying that only POSIX-compatible shells should set
Thanks Behdad,
The problem is that I do not have root permissions on the system with the
faulty '/bin/sh': I cannot change '/bin/sh' and need to build my programs with
a custom shell.
If the user specifies a wrong shell (not the default '/bin/sh'), it is their
own responsibility that it is
Do you mean here?
https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
There is only 'configure.raw' there; its contents are indeed Autoconf,
but its name is non-standard, that is probably why I missed it ;-).
The main point is that the 'configure' script at the top
Welcome back, Ahmet!
I look forward to working with you over the summer. We have a warm-up
month to chat about the project without any specific goals.
I suggest that you play with our demos using XQuartz backend, research
possible macOS native API and ask Suzuki some random questions about
it.
Scratch that.
Where is it exactly failing? On Unix, the build system is essentially
autoconf, so it should respect SHELL as you suggest.
behdad
http://behdad.org/
On Wed, May 1, 2024 at 3:15 PM Behdad Esfahbod wrote:
> Can you check if also setting CONFIG_SHELL helps?
>
> behdad
>
I had set the 'SHELL' environment variable but still '/bin/sh' was used.
The only way I could pass my SHELL to the Make command within the
configure script was through the non-standard hack I mentioned before:
GNUMAKE="make SHELL=$SHELL"
Autoconf generates the './configure' script
Dear Ahmet,
Congratulation! I'm glad to find another macOS contributor in
FreeType.
Please could you provide the updated estimation of the schedule,
with new goal (native graphics backend for macOS, without X11)?
The filed schedule dated on April 2nd was written for older goal
(an improvement
>>
>> Do you mean here?
>>
>> https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
>> ...
>
> Please start at README and README.git or here:
> https://gitlab.freedesktop.org/freetype/freetype/-/blob/master/docs/INSTALL.UNIX
>
> There is this peculiar autogen.sh to be run
Hi Suzuki,
Thank you, I am so excited to work with you!
The new goal is Native Graphics Backend for FreeType Demos on macOS.
I have updated on the GSoC website but the proposal file is unable to change.
Here you can find my proposal in the attachments.
Best,
Goksu
goksu.in
On May 2, 2024 at
I know all that. :) Check out builds/unix/configure.ac
behdad
http://behdad.org/
On Wed, May 1, 2024 at 4:40 PM Mohammad Akhlaghi
wrote:
> I had set the 'SHELL' environment variable but still '/bin/sh' was used.
> The only way I could pass my SHELL to the Make command within the
> configure
Can you check if also setting CONFIG_SHELL helps?
behdad
http://behdad.org/
On Wed, May 1, 2024 at 3:06 PM Mohammad Akhlaghi
wrote:
> The Autoconf-generated configure script, or even CMake, respect SHELL, so
> if a user gives it a problematic shell, they won't be able to build
> anything abd
On Wed, May 1, 2024 at 7:11 PM Mohammad Akhlaghi wrote:
>
> Do you mean here?
>
> https://gitlab.freedesktop.org/freetype/freetype/-/tree/master/builds/unix
> ...
Please start at README and README.git or here:
https://gitlab.freedesktop.org/freetype/freetype/-/blob/master/docs/INSTALL.UNIX
17 matches
Mail list logo
