Compiling on Mountain Lion

First I got:

Renaming "#include <GL/gl.h>" to "#include <OpenGL/gl.h>" in B3dAcceleratorPlugin.h fixed that problem, but then I got:
"rmdir: /Users/sean/Documents/Reference/Squeak/Cog/2012-09/cog/build/thirdparty/out/include/freetype2/freetype/internal: No such file or directory"

Any ideas?

Thanks,
Sean

how are you generating the sources, etc.? I need more data than that... :)

On Sep 10, 2012, at 8:35 PM, "Sean P. DeNigris" <[hidden email]> wrote:

EstebanLM wrote

how are you generating the sources, etc.?

1. Downloaded latest vmmaker and cog sources from Jenkins git tracker
2. CogCocoaIOSConfig new
  addExternalPlugins: #( FT2Plugin );
  addInternalPlugins: #( UnixOSProcessPlugin );
  generateForDebug;
  generateSources; generate.
3. cog/build$ /opt/local/bin/cmake -G Xcode

that's the problem :)

you cannot generate freetype2 with Xcode.

better try:

cmake .
make

On Sep 10, 2012, at 8:50 PM, "Sean P. DeNigris" <[hidden email]> wrote:

ah, btw... it *should* be possible with xcode, but I never took time to configure it...

On Sep 10, 2012, at 8:53 PM, Esteban Lorenzano <[hidden email]> wrote:

I had besides a hardcoded compiler path no problem.
Though I didn't use the latest vmmaker image, but the one from jenkins...

I used the Makefile builds, which worked nicely...

On 2012-09-10, at 20:36, "Sean P. DeNigris" <[hidden email]> wrote:

 
On 10 September 2012 20:35, Sean P. DeNigris <[hidden email]> wrote:
>
> First I got:
>
> Renaming "#include <GL/gl.h>" to "#include <OpenGL/gl.h>" in
> B3dAcceleratorPlugin.h fixed that problem, but then I got:
> "rmdir:
> /Users/sean/Documents/Reference/Squeak/Cog/2012-09/cog/build/thirdparty/out/include/freetype2/freetype/internal:
> No such file or directory"
>
this is strange.. the
thirdparty/out
subdir is where the built artifacts are placed by freetype itself,
means there's nothing in cmake config which tells to remove that
specific dir.
it looks like some bug in freetype library own 'make install'
procedure, because i only telling it that install prefix should be
<builddir>/thirdparty/out , and freetype should do the rest.

At which stage you get that error?
Can you try to reproduce it, after cleaning build dir and then doing

cmake .

do

make freetype

to see if get same error?



--
Best regards,
Igor Stasenko.

Igor Stasenko wrote

At which stage you get that error?
Can you try to reproduce it, after cleaning build dir and then doing

cmake .

do

make freetype

to see if get same error?

make freetype
make: *** No rule to make target `freetype'.  Stop.

but

make freetype2
[100%] Built target freetype2

I'm attaching (to Nabble) the full output of the freetype script failure from Xcode

HTH,
Sean

is

make freetype2


On Sep 11, 2012, at 6:33 PM, "Sean P. DeNigris" <[hidden email]> wrote:

EstebanLM wrote

you cannot generate freetype2 with Xcode.

better try:

cmake .
make

I want to build with Xcode because I am debugging and want to use the breakpoint tools, but I'll just compile without freetype

Thanks.

EstebanLM wrote

is

make freetype2
> make freetype2
> [100%] Built target freetype2
>

Yes

 
On 11 September 2012 18:36, Sean P. DeNigris <[hidden email]> wrote: yeah, just exclude ft2plugin from build.
:)
> Thanks.
>
>
>
> --
> View this message in context: http://forum.world.st/Compiling-on-Mountain-Lion-tp4646885p4647016.html
> Sent from the Squeak VM mailing list archive at Nabble.com.



--
Best regards,
Igor Stasenko.

yep... that's what I do :)

On Sep 11, 2012, at 6:36 PM, Sean P. DeNigris <[hidden email]> wrote:

On 2012-09-11, at 19:24, Esteban Lorenzano <[hidden email]> wrote:

I think I accidentally compiled freetype using make then changed regenerated the
project using cmake -G Xcode and I have freetype running :)

yes, that works too :P
we need something better, but xcode is not the funniest piece of software :S

On Sep 11, 2012, at 7:26 PM, Camillo Bruni <[hidden email]> wrote:

On 2012-09-11, at 19:27, Esteban Lorenzano <[hidden email]> wrote:
> yes, that works too :P
> we need something better, but xcode is not the funniest piece of software :S

true :) If there were a brilliant standalone C/C++ debugger there would be
no need for xcode :)

EstebanLM wrote

xcode is not the funniest piece of software :S

Opening the giant C file for the main VM loop was really fun in Xcode on Lion because it meant I could take a nice coffee break while it opened the file :)

 
On 11 September 2012 19:32, Sean P. DeNigris <[hidden email]> wrote: cannot add anything to that.
definitely, xcode editor was not designed to handle multi-megabyte
source files well :)
but i think if you disable syntax highlighting and other niceties in
editor, it should handle it fine,
because my suspicion is that it wastes a lot of time for parsing it to
do a proper syntax highlighting.

>
>
> --
> View this message in context: http://forum.world.st/Compiling-on-Mountain-Lion-tp4646885p4647029.html
> Sent from the Squeak VM mailing list archive at Nabble.com.



--
Best regards,
Igor Stasenko.