Help compiling SciTe on windows

[Alien Burn]

Anyone know of good guides to compiling SciTE on windows. I want to
mess with it bit. I have the source files but there doesn't seem to be
any makefiles in the windows directory or any README or INSTALL. I
added all the files to a new DevC++ project expecting it to compile
but it didn't. It kept asking for header files that were present in
another folder. I kept adding the files needed but soon gave up. It
was too tedious. Any help?

[KHMan]

Yes, there is a Win32 makefile. If you just state "in the windows
directory", there is no way anyone here can properly diagnose
anything with that information. We can only guess at most...

(1) Get the sources
(2) Make sure you got a /scintilla tree and a /scite tree
(3) Find the makefile
(4) Go to the makefile directory and do the usual things

Compiling is dead easy on MinGW or MinGW/TDM. If you are stuck on
any of the above steps, please provide enough information for us
to make at least useful guesses.

--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia

[Neil Hodgson]

Alien Burn:

> but there doesn't seem to be
> any makefiles in the windows directory or any README or INSTALL.

There should be a README in both the scintilla and scite directories and it should look like
http://sourceforge.net/p/scintilla/scite/ci/853e303a331f23b543f68065a7a92a0369ac2c25/tree/README

Neil

[Alien Burn]

Looks like the makefile is there. I must have been blind the first time. I've tried to compile it(with fingers crossed), but it fails to create the scintilla dll so scite doesn't start.
I get this when building scintilla:
mingw32-make: *** [../bin/Scintilla.dll] Error 1
And this when building scite:
mingw32-make: *** No rule to make target `ScintillaWinL.o' needed by `../bin/Sc1.exe'. Stop.
The README in scite said try gtk+(not sure if it's same as gtk) but it failed miserably. The same happened when I tried it in .\scite333-source\scite\gtk

[KHMan]

Well, if you show the command line and path, it might be easier to
diagnose. Remember, you are supposed to help us help you.

[Alien Burn]

Haha, it finally worked. This has been the best compiling experience ever. The problem was one of the options being passed to the linker set in the scintilla makefile. It had --enable-runtime-pseudo-reloc-v2 while my linker version was 2.15.91. I only had to remove the '-v2' and I was smiling all the way(thanks to little googling). I guess I wasn't giving you the right information.
I have another somewhat ignorant question though. How come there are so many warnings like
../src/Editor.cxx:3173 warning: converting to `int' from `float'.
The line is:
int xIndent = indentCount * indentWidth;
Shouldn't there be a type cast here?
(i had to delete my earlier post to correct the file name with the warning)

[KHMan]

Gee, what version of gcc are you on? Even my ancient installation
of gcc 3.4.5 MinGW reports ld as 2.19...

It's best to compile with a recent gcc, >=4.7.x (this will take
care of your linker problem too.) Older gcc versions will spew out
different warnings.

[Alien Burn]

GNU Make 3.8.0
Thread model: win32
gcc version 3.4.2(mingw-special)
GNU ld version 2.15.91 20040904
I've tried compiling with the gmake that comes with Dwimperl which uses ld version 2.21.90.20111031 but it still complains about an 'unrecognized option '--enable-runtime-pseudo-reloc-v2'. The only workaround is removing '-v2'. Another question, why does it generate Sc1.exe which is almost twice as large as scite.exe?

[KHMan]

Okay, I guess you installed Dev-C++ 4.9.9.2 from Feb 2005. That
was released 8 years ago. :-)

Many things are not gonna compile right on gcc <=3.4.5 if they
have moved to the 4.x.x series. Often there will be many warnings,
or worse. Of course gcc 3.4.2 still work for many things, but you
may not find many people still on it. Active projects would
probably be using the newer gcc.

Perhaps you should go for
http://sf.net/projects/orwelldevcpp/
instead. (But I use MSYS and makefiles so I have never tested it,
so this is not an endorsement.) Or just install the latest TDM gcc
from
http://tdm-gcc.tdragon.net/
and use SciTE.

Sc1.exe is statically-linked and self-contained. See
http://www.scintilla.org/SciTEDownload.html

[Alien Burn]

Haha, I didn't see the point of going for Orwell or even Code blocks. I could save some megabytes by getting the 9mb Dev C++(internet connectivity costs a lot in my country). On top of that, I don't do a lot of C/C++. Thanks a lot anyway.

[KHMan]

On 8/25/2013 11:52 PM, Alien Burn wrote:
> Haha, I didn't see the point of going for Orwell or even Code blocks. I could save some megabytes by getting the 9mb Dev C++(internet connectivity costs a lot in my country). On top of that, I don't do a lot of C/C++. Thanks a lot anyway.

Okay, just be aware that if you are compiling substantial things
like Scintilla/SciTE and run into problems specific to gcc3, then
you will likely get very little direct help where devs have moved
on to gcc4. You might have to rely on troubleshooting with the
help of Google. (Which is not a bad thing, since pre-Internet most
of us debugged programs by ourselves...) Good luck.