Re: [hatari-devel] Is it me or the new hatari release is slow ?

[Laurent Sallafranque <laurent.sallafranque@xxxxxxx>]

OK, it works and I understand now how it works.

I encounter a new problem : the version selected by the bisect gives 
some compiling errors :

[ 61%] Building C object src/CMakeFiles/hatari.dir/floppy_ipf.c.o
/home/laurent/Atari/hatari/src/floppy_ipf.c: In function 
‘IPF_Drive_Update_Enable’:
/home/laurent/Atari/hatari/src/floppy_ipf.c:566:16: erreur: ‘IPF_STRUCT’ 
has no member named ‘DriveEnabled’
/home/laurent/Atari/hatari/src/floppy_ipf.c:567:19: erreur: ‘IPF_STRUCT’ 
has no member named ‘Fdc’
/home/laurent/Atari/hatari/src/floppy_ipf.c:569:19: erreur: ‘IPF_STRUCT’ 
has no member named ‘Fdc’


So I don't know if this version is --good or --bad

Laurent



Le 01/06/2014 13:21, Thomas Huth a écrit :
> Am Sun, 01 Jun 2014 13:15:49 +0200
> schrieb Laurent Sallafranque <laurent.sallafranque@xxxxxxx>:
>
> > Thanks thomas,
> >
> > But I always get the following error :
> >
> > laurent@OrdiLoloLinux:~/Atari/hatari/build$ hg bisect --good v1.7.0
> > Testing changeset 4887:a19fee326303 (443 changesets remaining, ~8
> > tests) abandon : outstanding uncommitted changes
> > laurent@OrdiLoloLinux:~/Atari/hatari/build$
> >
> >
> > Is it due to the change in CmakeList.txt.
> Yes.
>
> > I change the
> >
> > set(ENABLE_WINUAE_CPU 1
> >       CACHE BOOL "Enable WinUAE CPU core (experimental!)")
> >
> >
> > to compile with the new cpu
> You should never change CMakeList.txt for configuring your build.
> Either use "./configure --enable-winuae-cpu" or if you prefer to
> call it directly use "cmake -DENABLE_WINUAE_CPU:BOOL=1 ." instead.
>
>   Thomas