Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set backwards nx,ny to n_cols, n_rows in 6.1 #3572

Closed
wants to merge 1 commit into from

Conversation

PaulWessel
Copy link
Member

Because of the ubuntus of the world, people are failing to build GMT and GMTSAR since we removed the backward nx,ny settings. This reinstate those settings just for GRIDs since that is the only thing GMTSAR uses. I figure we can eventually remove that when ubuntu 16 dies or the people using it dies or stop using GMTSAR. This will help in the short term and will be in 6.1

Because of the ubuntus of the world, people are failing to build GMT and GMTSAR since we removed the backward nx,ny settings.  This reinstate those settings just for GRIDs since that is the only thing GMTSAR uses.
@joa-quim
Copy link
Member

joa-quim commented Jul 2, 2020

This will break Julia

@PaulWessel
Copy link
Member Author

Explain. it was always there until a few weeks ago?

@joa-quim
Copy link
Member

joa-quim commented Jul 2, 2020

Not in GMT_GRID_HEADER that is not changed in 3 years. Changing it that's what would break Julia

@PaulWessel
Copy link
Member Author

I only put back a subset of what as in GMT until a few weeks/months ago, and only the grid stuff. I did not do the CPT and DATASET parts. The nx,ny was in the grid header until very recently. So how did Julia work 2-3 months ago that is different from now w.r.t gmt_resources.h?

@PaulWessel
Copy link
Member Author

I can understand if you made changes to match our changes in the last 1-2 months on this, but otherwise I dont see why it would matter to Julia.

@joa-quim
Copy link
Member

joa-quim commented Jul 2, 2020

No I didn't and I can't be doing it all the time. Maybe it worked because those 2 were at the end of the members list and hence forgotten by the julia struct

#ifdef GMT_BACKWARDS_API
	uint32_t nx;
	uint32_t ny;
#endif

The #ifdef doesn't help here because GMT_BACKWARDS_API is defined unconditionally . The corresponding Julia struct is here

@PaulWessel
Copy link
Member Author

If it continuous to work for Julia (as before), then presumably not a problem for you?

@joa-quim
Copy link
Member

joa-quim commented Jul 2, 2020

Now that I see it was not conditionally include the situation is of a clear breaking, waiting to manifest mysteriously someday when something try to access those 8 bytes left in the ether.

@PaulWessel
Copy link
Member Author

Well, I would rather have it break for someone using 5.2 with GMTSAR than for Julia to break with 6.1. So we will delete that PR and move on.

@PaulWessel PaulWessel closed this Jul 2, 2020
@PaulWessel PaulWessel deleted the reinstate-nx-ny branch July 2, 2020 01:51
@joa-quim
Copy link
Member

joa-quim commented Jul 2, 2020

But those have no problems with this. For what I understand is really GMTSAR that must update if it wants to use 6.1, and it's nothing complicated to do.

@PaulWessel
Copy link
Member Author

GMTSAR has updated, but if you download GMTSAR now and want to build with GMT 5.2... no more nx, ny.

@PaulWessel PaulWessel restored the reinstate-nx-ny branch July 9, 2020 02:00
@seisman seisman mentioned this pull request Jul 9, 2020
@PaulWessel
Copy link
Member Author

I think I have exceeded my number of branches in two weeks. This is almost funny. OK, will un-restore that branch once again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants